skills/commit/SKILL.md
Stage and commit changes with a conventional commit message. Runs pre-commit checks automatically. Optionally prefixes with a ticket number.
npx skillsauth add nexus-a1/claude-skills commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Recent commits for reference: !git log --oneline -5 2>/dev/null || echo "No previous commits (this will be the first commit)"
Current branch: !git branch --show-current 2>/dev/null || echo "(not in a git repository)"
Run everything inline — no agent delegation. The git-mutation-guard.sh PreToolUse hook runs the credential scan on staged files automatically at commit time; you do not need to scan separately.
Priority order (argument: $ARGUMENTS):
[A-Z]+-[0-9]+.branch=$(git branch --show-current)
ticket=$(echo "$branch" | grep -oE '[A-Z]+-[0-9]+' | head -1)
The ticket MUST appear in the commit message as [TICKET-123] (brackets, original casing).
If on main or master, create a feature branch before committing:
git checkout -b feature/[ticket]-description
test -f ./vendor/bin/php-cs-fixer && ./vendor/bin/php-cs-fixer fix --dry-run --diff <modified-php-files>
Skip silently if not available or no PHP files modified.
Use compact flags — never plain git status / git diff:
git status --short
git diff --stat HEAD
Identify files to stage, excluding .env*, credentials.*, *.pem, *.key. For files whose content you need to understand for the commit message, fetch the full patch per-file:
git diff HEAD -- <file>
Stage explicitly:
git add <file1> <file2> ...
Format:
[TICKET-123] type(scope): short description
Optional body wrapped at 72 chars explaining the WHY.
Types: feat | fix | refactor | test | docs | chore | style | perf
Rules:
Co-Authored-By, NO Generated with Claude Code, NO AI attributiongit commit -m "$(cat <<'EOF'
[TICKET-123] type(scope): short description
Optional body.
EOF
)"
If the hook blocks the commit due to a credential-scan finding: surface the finding to the user verbatim (file:line — label, never the secret value). Ask whether it is a true leak or false positive. On confirmed false positive, re-run with GIT_AUTHORIZED=1 git commit … and include the reason in the commit body so the override is traceable. Never override silently.
Show:
git log -1 --format='%h')git show --stat HEAD)development
Add a new entry to the product knowledge base. Wizard-guided — prompts for category, title, and content, then writes a structured markdown file and rebuilds the manifest.
data-ai
Show all active work sessions across brainstorms, requirements, proposals, and epics. Supports --update to advance lifecycle on one session and --sync to sweep them all.
documentation
Review and update project documentation using an agent team. Inventories docs, identifies gaps and drift, updates technical and API docs in parallel.
tools
Annotate an active work session with a note, scope change, or new finding. Auto-detects the active session, synthesizes the salient points of the current conversation, and appends a timestamped entry to state.json after a single target confirmation. Use mid-session when you learn something that should be preserved.