Validated Commit
SkillDev toolsValidated commit — runs quick checks before committing. Use when ready to commit changes.
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 Validated Commit skill
What this skill tells your AI
The instructions your AI receives, as published by stevegjones/ai-first-sdlc-practices in skills/commit/SKILL.md and read by ahel’s review.
Run quick validation, then commit if clean.
Steps
- Run quick validation
/sdlc-core:validate --quick
- Run tests and smoke test (if application code was changed)
# Run test suite if configured
pytest --tb=short -q 2>/dev/null || echo "No pytest configured"
# Smoke test: verify the app's main module imports cleanly
python -c "import app" 2>/dev/null || python -c "import main" 2>/dev/null || echo "No app module found"
If tests fail or the app cannot import, stop. Fix the issue before committing. Static analysis passing does not mean the code works.
-
If validation or tests fail, report the issues and stop. Do NOT commit.
-
If all checks pass, proceed:
- Review all changed files with
git statusandgit diff - Stage the relevant files (prefer specific files over
git add -A) - If
$ARGUMENTSis provided, use it as the commit message - If no message provided, draft a concise commit message based on the changes
- Use conventional commit format:
feat:,fix:,docs:,refactor:,test:,chore:
- Review all changed files with
-
Commit using a heredoc for proper formatting:
git commit -m "$(cat <<'EOF'
<type>: <description>
<optional body>
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
- Run git status after commit to verify success.
Signals
- GitHub stars
- 41
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
commit-stevegjones- Source
- github.com/stevegjones/ai-first-sdlc-practices