Zplit
F 50 completed
Other
unknown / zig · tiny
22
Files
5,804
LOC
0
Frameworks
2
Languages
Pipeline State
completedRun ID
#1504756Phase
doneProgress
0%Started
2026-04-16 12:59:46Finished
2026-04-16 12:59:46LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
27.13Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #49193
Member of a group with 43 similar repo(s) — canonical #1591863 view group →
Repobility · code-quality intelligence · https://repobility.com
AI Prompt
Create a command-line terminal multiplexer similar to tmux, but written in Zig. The tool needs to support pane splitting (horizontal and vertical), tab management, and session persistence so that layouts are saved when detaching. Key features to include are text reflow when the terminal width changes, full CJK character support, and the ability to run in an alternate screen. It should aim to be a single, statically linked binary with zero runtime dependencies, ideally keeping the size under 100KB.
zig cli terminal multiplexer ncurses command-line pane-splitting session-management
Generated by gemma4:latest
Catalog Information
Create a command-line terminal multiplexer similar to tmux, but written in Zig. The tool needs to support pane splitting (horizontal and vertical), tab management, and session persistence so that layouts are saved when detaching. Key features to include are text reflow when the terminal width changes, full CJK character support, and the ability to run in an alternate screen. It should aim to be a single, statically linked binary with zero runtime dependencies, ideally keeping the size under 100K
Tags
zig cli terminal multiplexer ncurses command-line pane-splitting session-management
Quality Score
F
49.9/100
Structure
50
Code Quality
42
Documentation
52
Testing
0
Practices
78
Security
100
Dependencies
50
Strengths
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Properly licensed project
Weaknesses
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
- 1037 duplicate lines detected — consider DRY refactoring
- 4 'god files' with >500 LOC need decomposition
Recommendations
- Add a test suite — start with critical path integration tests
- 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:
