Menu
Commit timing rules for this project. Use when committing code, pushing changes, finishing a task, or deciding when to create a git commit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Documentation sync after code review. Use when resolving PR review comments, fixing code from review feedback, adding new files or components, or changing architectural patterns.
Controls the Ghostty terminal emulator via CLI actions and configuration. Use when managing Ghostty windows, fonts, themes, keybinds, config validation, or debugging terminal configuration. Use for ghostty CLI, terminal config, theme selection, font management.
GitHub CLI workflows for repositories, issues, pull requests, actions, releases, projects, and API calls. Use when creating PRs, reviewing code, triaging issues, triggering workflows, publishing releases, managing projects, verifying attestations, or querying the GitHub API. Use for gh cli, github automation, code review, release management.
Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction.
Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use when triaging beads tasks, analyzing dependency graphs, finding bottlenecks, detecting circular dependencies, planning parallel execution tracks, or generating sprint burndown data.
Converts markdown plans into beads (tasks with dependencies) and polishes them until implementation-ready. The bridge between planning and agent team execution. Use when converting a plan to beads, polishing bead descriptions, adding test coverage beads, reviewing bead dependencies, or preparing tasks for parallel agent team execution.
| name | commit-discipline |
| description | Commit timing rules for this project. Use when committing code, pushing changes, finishing a task, or deciding when to create a git commit. |
| user-invocable | false |
If the user is actively in the conversation — asking questions, giving feedback, requesting changes, or iterating on something — do NOT commit. The conversation is still in progress. Wait until:
Signs you are in an interactive iteration:
Multiple files changed for the same logical purpose = one commit, not one commit per file. If you edited a template, an instruction file, and a docs file all for "improve PR template" — that is one commit.
