commit
Commit
Quick start
When user triggers /commit or asks to commit:
- Run
git add -Ato stage all changes - Run
git statusandgit diff --stagedto review changes - Draft a conventional commit message (
type(scope): subject) - Present summary + commit message to user
- Ask for confirmation via
questiontool - If confirmed:
git commit -m "message"
Workflow
1. Stage all changes
Run git add -A to stage all modified, added, and deleted files.
More from ishakantony/skills
discuss
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. DO NOT EVER USE THIS SKILL UNLESS THE USER EXPLICITLY ASKS YOU TO.
19prd-to-issues
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.
15tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
14write-a-prd
Generate a PRD from the client brief and write it as a local markdown file in issues/. Use when the user wants to turn a client request into a structured PRD.
14tackle-issues
Autonomously work through AFK issues from the local issues/ directory in a loop, spawning a subagent per task. Use when user types /tackle-issues or asks to "work the backlog", "burn down issues", "tackle AFK tasks", or run an AFK issue queue. Skips HITL issues. Each task is implemented via TDD in a subagent so the main context stays clean.
13write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
9