shipit-kit:status

To check feature branch status, the skill reads git branch info, specs/NNN-* feature.yaml, tasks.yaml, and recent commits to summarize completed work and output remaining tasks. It synthesizes branch context into a concise progress report with a single clear next action.

ShipIT spec tracking organizes feature development using specs/NNN-* directories containing feature.yaml, tasks.yaml, and spec.yaml. You need it when resuming paused agent sessions or onboarding reviewers, as it synthesizes task state and commit history to provide immediate context without manual hunting.

Getting next steps involves analyzing task states from tasks.yaml alongside recent git commit history. The skill delivers precise verification steps to try the feature locally, listing remaining tasks or blockers and providing a single actionable next step so development can resume immediately.

Yes, this feature status tool applies specifically to repositories using ShipIT specs. It requires read access to the repository to inspect specs/NNN-* feature directories, run git commands, and read spec files like feature.yaml and tasks.yaml to determine completed work and remaining tasks.

You can confirm PR readiness by having the skill summarize completed work from commits and task states. It lists remaining tasks or blockers and provides explicit verification steps, allowing you to assess whether the feature branch is ready before opening a pull request.

The best way to orient a reviewer is generating a concise status report that synthesizes branch info, spec files, and recent commits. The skill provides a short actionable summary with explicit verification steps, enabling reviewers to understand feature status and test locally without searching for context.