commit-changes vs frb-debugging
commit-changes and frb-debugging are both developer tools skills. frb-debugging scores higher (84 vs 78 out of 100). commit-changes has more GitHub stars (51k), and commit-changes was updated more recently (2 days ago). The table compares them side by side.
| commit-changes | frb-debugging | |
|---|---|---|
| Score | 78 / 100 | 84 / 100 |
| What it does | Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context. | Use when generated code looks wrong, code generation fails, or you need to understand FRB internals |
| Publisher | Community: tldraw | Community: fzyzcjy |
| Grades | Maintenance A, Licence F, Quality A | Maintenance A, Licence A, Quality A |
| npm downloads a week | Not on npm | Not on npm |
| Runs | Skill | Skill |
| Works with | Claude Code, Claude apps | Claude Code, Claude apps |
| GitHub stars | 51,002 | 5,460 |
| Last commit | 19 Oct 2026 | 19 Oct 2026 |
| Licence | NOASSERTION | MIT |
| Listed since | 20 Oct 2026 | 20 Oct 2026 |
| Install commit-changes | Install frb-debugging |
Questions
Is commit-changes or frb-debugging more popular?
commit-changes has more GitHub stars: 51,002.
Can I use commit-changes and frb-debugging together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.