Skip to content

DavidROliverBA/ArchitectKB / .claude/skills/commit

commit

Verified

Stage and commit vault changes with UK English conventional commit messages

Commit Vault Changes

Stage and commit changes to the vault with properly formatted UK English conventional commit messages.

Usage

/commit                    # Auto-detect changes and commit
/commit -m "message"       # Commit with a specific message
/commit --amend            # Amend the previous commit (use sparingly)

Workflow

1. Review Changes

git status
git diff --stat

2. Stage Changes

Stage specific files rather than using git add -A:

  • Never stage: .env, credentials, .secrets.baseline (unless updated by detect-secrets)
  • Use git add -u for modified/deleted files with Unicode filenames (avoids octal encoding issues)
  • Use git lfs track first for large binary files (PPTX, PDF >100MB)

3. Compose Commit Message

Follow these conventions:

  • UK English spelling (e.g., "organise", "summarise", "colour")
  • Imperative mood in subject line (e.g., "Add meeting note" not "Added meeting note")
  • Subject line under 72 characters
  • Body explains the "why" not the "what" (the diff shows the what)
  • Always include the co-author tag

4. Commit Format

<type>: <subject>

<optional body>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Types:

TypeWhen to Use
AddNew notes, skills, scripts, templates
UpdateEnhancements to existing notes or config
FixBug fixes, broken links, frontmatter errors
RefactorRestructuring without changing meaning
ArchiveMoving notes to Archive/
RemoveDeleting deprecated content
DocsDocumentation-only changes (CLAUDE.md, READMEs)

5. Pre-commit Checks

The vault has pre-commit hooks that may:

  • Run detect-secrets (may need .secrets.baseline update)
  • Check for large files (use git LFS for >100MB)
  • Fix trailing whitespace and EOF

If the hook modifies files, re-stage with git add -u then commit again.

6. Post-commit

Run git status to verify the commit succeeded and working tree is clean.

Important

  • Never force push to main without explicit user confirmation
  • Never use --no-verify unless the user explicitly requests it
  • If git commit fails with PermissionError on ~/.cache/pre-commit/, use dangerouslyDisableSandbox: true
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexVerifiedInstall