.claude/skills/commit/SKILL.md
Stage relevant files and create a commit following Documents/Process/GitWorkFlow.md format. Auto-detects [BIZ-QC-NEEDED] requirement and prompts for sign-off note when applicable.
npx skillsauth add RahmanBhuiyan/monthly-budget-planning-rd .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.
You are creating a commit for the current branch's work.
Before doing anything:
git branch --show-current. If the branch is master or main, stop — the PreToolUse hook will block the commit anyway. Branch off first.git status and git diff to see what's changed.git log --oneline -5 to see recent commit message style.Per Documents/Process/CodeCommunityStandard.md and CLAUDE.md "Forbidden by default":
git add -A or git add . — they sweep up unrelated changes..env, *.db, *.sqlite3, anything matching .gitignore.If the diff touches any of:
backend/routes/budget.pybackend/routes/reports.pybackend/routes/expenses.pybackend/models.py…this is a [BIZ-QC-NEEDED] change per CLAUDE.md Rule 2. The commit body MUST include [BIZ-QC-NEEDED] AND should reference product-owner sign-off (Documents/Process/RACI.md W3). If sign-off is absent, prompt the user before committing.
Format from Documents/Process/GitWorkFlow.md §4:
type(scope): short imperative title
<body — explain the *why*, not the *what*. Bullet points OK.>
[BIZ-QC-NEEDED] ← only if the diff touches protected files
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Allowed types: feat, fix, hotfix, refactor, test, docs, chore, style, perf
Allowed scopes: auth, income, budget, expenses, dashboard, reports, alerts, summary, api, ui, infra, governance
Pick the type from what the diff actually does:
featfix (or hotfix if production-down)refactortestdocschoregit push --force (any branch)git commit --no-verifygit commit --amend on commits that have been pushedUse a HEREDOC so the message format survives shell quoting:
git commit -m "$(cat <<'EOF'
type(scope): title
Body explaining why.
[BIZ-QC-NEEDED]
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
EOF
)"
After commit, run git status to confirm a clean tree (or surface what's intentionally left).
Do not push unless the user explicitly asks. Even then, never to master directly — push the current feature branch.
development
Generate a weekly summary of commits on master — categorized highlights, statistics, and draft email/standup notes. Useful for sprint retros and release notes.
development
Read recent code changes and update the affected docs under Documents/. Documents the *current* state, not history. Use after a feature lands or when docs have drifted.
testing
# Statusline Setup — Smart Expense & Budget Tracker A two-row statusline tailored for this project's SDLC workflow. Adapted from [fotoflo/claude-skills](https://github.com/fotoflo/claude-skills/tree/main/statusline-setup). ## What you see **Row 1 — project context** ``` ~/project/monthly-budget-planning-rd (feature/audit-deep-read) [opus] session-name #BUG-1 [BIZ-QC ✓] ``` | Element | Meaning | |---------|---------| | `~/project/...` (green) | Current working directory | | `(branch)` (c
development
Run the pre-flight checklist from Documents/DevOps/ReleaseRunbook.md before cutting a release. Reports PASS or BLOCKED with specific reasons.