From stdd-agents
Use when creating git commits. Defines conventional commit format and message structure guidelines.
npx claudepluginhub craigtkhill/stdd-agents --plugin stdd-agentsThis skill uses the workspace's default tool permissions.
Guidelines for writing clear, consistent git commit messages.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Guidelines for writing clear, consistent git commit messages.
Use the conventional commits style:
<type>[optional scope]: <description>
CRITICAL: Single-line only. Never add a body or footer. The code and spec speak for themselves.
Add scope in parentheses to provide additional context:
Indicate breaking changes with ! after type/scope:
Never add a commit body or footer. Every commit must be a single line only.
Do NOT include AI attribution, co-authored-by lines, or any other footers.
CRITICAL — all of the following MUST be true before committing:
prek run --all-files and fix every issuegit fetchgit status and git diffgit add <files>❌ NEVER commit with failing tests ❌ NEVER commit without running pre-commit hooks ❌ NEVER commit half-finished work
Commit once per completed requirement in the STDD cycle:
spec written → tests RED → tests GREEN → hooks pass → COMMIT
When following the spec-test-driven development workflow:
prek run --all-files → all hooks pass