Tabflow.Nvim
C 63 completed
Other
containerized / lua · tiny
31
Files
1,866
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1367432Phase
doneProgress
0%Started
2026-04-16 03:43:48Finished
2026-04-16 03:43:48LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
23.95Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:10Deduplication group #52348
Member of a group with 22 similar repo(s) — canonical #1076592 view group →
Repobility · MCP-ready · https://repobility.com
AI Prompt
Create a Neovim plugin, similar to tabflow.nvim, that provides an IDE-style tabpage and buffer navigation system for Neovim 0.11+. I need it to support two modes: managing workspaces (tab pages) and managing buffers within the current workspace. Key features must include Git integration, automatically setting tab names to the current git branch name, and a command to open an existing git worktree in a new tab. It should also support full mouse interaction for switching, closing, renaming, and reordering tabs and buffers. Finally, include commands for toggling between tab and buffer modes, and for navigating between tabs and buffers.
lua neovim plugin vim ui git editor navigation
Generated by gemma4:latest
Catalog Information
Create a Neovim plugin, similar to tabflow.nvim, that provides an IDE-style tabpage and buffer navigation system for Neovim 0.11+. I need it to support two modes: managing workspaces (tab pages) and managing buffers within the current workspace. Key features must include Git integration, automatically setting tab names to the current git branch name, and a command to open an existing git worktree in a new tab. It should also support full mouse interaction for switching, closing, renaming, and re
Tags
lua neovim plugin vim ui git editor navigation
Quality Score
C
62.9/100
Structure
69
Code Quality
47
Documentation
35
Testing
70
Practices
78
Security
100
Dependencies
50
Strengths
- Good test coverage (50% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Containerized deployment (Docker)
- Properly licensed project
Weaknesses
- No CI/CD configuration — manual testing and deployment
- 1 files with critical complexity need refactoring
- 203 duplicate lines detected — consider DRY refactoring
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
Languages
Frameworks
None detected
Embed Badge
Add to your README:
