Git Discipline
SkillAI & modelsRead-only git guardrails and the Conventional Commits reference — no history writes, verify changes before completing. Triggered by planner-agent, implementer-agent, implementer-expert-agent, and recorder-agent. The headless orchestrators speq-plan-pr and speq-implement-pr are the sole exception: they write git history directly and use /speq-git-operations instead of this skill.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Git Discipline skill
What this skill tells your AI
The instructions your AI receives, as published by marconae/speq-skill in .claude/skills/speq-git-discipline/SKILL.md and read by ahel’s review.
Git read-only guardrails. User controls all git writes.
Allowed Commands
git status git diff git log git show git branch
Forbidden Commands
add commit push pull fetch
merge rebase cherry-pick
checkout switch restore
reset revert stash tag
No exceptions.
Before Completing Work
Verify expected changes:
git status # Check files changed
git diff # Review actual changes
Tracked vs Gitignored Spec Paths
- Everything under
specs/_plans/<plan-name>/is tracked and committed with the plan directory, never gitignored. This includes the evidence artifacts:open-questions.md(present only while the plan is blocked)review/(plan-review findings,round-<N>.md)review-findings.md(code-review findings)tasks.mdandverification-report.md
- These commits put the evidence trail into history before
/speq-recordarchives the plan (mv specs/_plans/<plan-name> specs/_recorded/NNN-<plan-name>). specs/_recorded/is gitignored by default. This is a default, not an enforced rule: a project can track_recorded/, and the archived plan then lands in history a second time./speq-audit's gitignore-hygiene checks default to this split (_plans/_decisiontracked,_recordedignored). They only offer to align a drifted project, never force it.
Security
Never commit secrets (API keys, passwords, credentials, tokens).
Commit Conventions
Follow the Conventional Commits specification:
<type>[scope]: <description>
[body]
[footer]
| Type | Use |
|---|---|
feat | New feature (MINOR) |
fix | Bug fix (PATCH) |
perf | Performance |
refactor | Restructure, same behavior |
test | Tests |
docs | Documentation |
spec | Spec changes |
chore | Maintenance |
Breaking changes: Add ! after type or BREAKING CHANGE: footer → MAJOR version
Signals
- GitHub stars
- 50
- Forks
- 9
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
speq-git-discipline- Source
- github.com/marconae/speq-skill