commit-task

Verifies planning document completeness and commits them to the main branch.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill commit-task-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-task
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/commit-task
Command: npx skills add https://github.com/mistakenot/skills --skill commit-task-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finalizing a task's planning phase requires checking that every planning document is complete, consistent, and reviewed before it lands on main; doing this by hand is error-prone and easy to skip. This Skill runs a structured verification checklist and commits the approved docs in one controlled step. ## Core Features & Use Cases - Completeness Verification: Checks that requirements.md, solution.md, context.md, and plan.md all exist, contain no unanswered open questions, and that every acceptance criterion is covered by tests and plan steps. - Consistency Checks: Confirms the plan matches the solution, context covers all plan references, no unresolved P1 review comments remain, and epic frontmatter is consistent across docs. - Status Advancement and Commit: Sets the task status to pending on the pd-doc element, commits the docs with a conventional commit message, pushes to origin main, and handles push failures with rebase or merge fallbacks. - Use Case: After reviewing and approving all planning docs for task 042-add-auth, run this Skill to verify everything is complete, commit the docs to main, and get the prompt to start implementation with /execute-task. ## Quick Start Commit the task planning docs for task 042 after verifying all documents are complete and approved.

Frequently Asked Questions about commit-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit task planning docs to main?▼

Run the commit-task skill after all planning docs are reviewed and approved. It verifies the four required files exist, checks for unanswered questions and unresolved P1 comments, then commits and pushes the docs to origin main with a conventional commit message.

What checks run before committing planning documents?▼

The checklist verifies all four files exist (requirements.md, solution.md, context.md, plan.md), no open questions remain, every acceptance criterion has test coverage and plan steps, the plan matches the solution, context covers plan references, no unresolved P1 comments exist, and epic frontmatter is consistent.

What happens if the git push to main fails?▼

The skill first tries git pull --rebase origin main and pushes again. If the rebase hits conflicts, it aborts and tries git pull --no-rebase instead. If that also fails, it stops and asks the user for help rather than force-pushing.

Does commit-task create a feature branch or start implementation?▼

No. It only commits planning docs to main and advances the task status to pending. It explicitly does not create a feature branch or begin implementation; that happens later with /execute-task in an isolated worktree.

When should I not use commit-task?▼

Do not use it when implementation has already started or when committing code changes. It is only for finalizing the planning stage by committing documentation, not for source code commits.