quantumbitcz/forge-commit
skills/forge-commit/SKILL.md
[writes] Generate terse conventional commit messages from staged changes. Use when you have staged files and want a well-structured commit message that follows Conventional Commits format. Analyzes diffs, infers type and scope, presents options.
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add quantumbitcz/dev-pipeline forge-commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 5:16 AM5.9s1 file scanned
SKILL.md
- name:
- forge-commit
- description:
- [writes] Generate terse conventional commit messages from staged changes. Use when you have staged files and want a well-structured commit message that follows Conventional Commits format. Analyzes diffs, infers type and scope, presents options.
- allowed-tools:
- ['Read', 'Write', 'Edit', 'Bash', 'Glob', 'Grep', 'Agent']
/forge-commit -- Terse Conventional Commit Generator
Analyzes staged changes and generates a Conventional Commits message. Subject line <=50 chars, body explains why (not what). Never includes AI attribution.
Flags
- --help: print usage and exit 0
- --dry-run: preview actions without writing
Exit codes
See shared/skill-contract.md for the standard exit-code table.
Prerequisites
- Git repository: Run
git rev-parse --show-toplevel 2>/dev/null. If fails: "Not a git repository." STOP. - Staged changes exist: Run
git diff --cached --stat. If empty: "No staged changes. Stage files withgit addfirst." STOP.
Instructions
1. Analyze Staged Changes
git diff --cached --stat
git diff --cached
Identify:
- Files changed -- count and paths
- Nature of change -- new feature, bug fix, refactor, test, docs, build, CI, style, perf, chore
- Scope -- module/component most affected (e.g.,
auth,api,build,ci) - Key behavioral change -- the "why" in one sentence
2. Determine Commit Type
Map changes to Conventional Commits types:
| Type | When |
|------|------|
| feat | New functionality visible to users or consumers |
| fix | Bug fix |
| refactor | Code restructuring without behavior change |
| test | Adding or updating tests only |
| docs | Documentation only |
| build | Build system or dependency changes |
| ci | CI/CD configuration |
| style | Formatting, whitespace, linting (no logic change) |
| perf | Performance improvement |
| chore | Maintenance tasks, version bumps |
If multiple types apply, use the most significant one (feat > fix > refactor > others).
3. Generate Commit Message
Subject line rules:
- Format:
type(scope): imperative description - Maximum 50 characters total
- Lowercase, no period at end
- Imperative mood: "add" not "added" or "adds"
- Scope is optional -- omit if change spans many modules
Body rules (if needed):
- Blank line after subject
- Explain WHY the change was made, not what changed (diff shows that)
- Wrap at 72 characters
- Reference ticket IDs if present in branch name or staged content
NEVER include:
- Co-Authored-By lines
- AI attribution of any kind
- Signed-off-by lines (unless project convention requires it)
4. Present Options
Use AskUserQuestion to present the generated commit:
Proposed commit:
type(scope): subject line here
Body explaining why (if applicable).
Options:
1. Commit as-is
2. Edit message (provide revised text)
3. Cancel
5. Execute
Based on user choice:
- Commit: Run
git commit -m "<message>"(or-m "<subject>" -m "<body>"if body present) - Edit: Accept user's revised message, then commit
- Cancel: "Commit cancelled." STOP.
After successful commit, report: Committed: <short-hash> <subject>
Terse Mode Integration
If .forge/caveman-mode exists and is not off, apply compression to all user-facing output:
lite: Drop filler, keep grammarfull:[type(scope)] subject. hash.ultra:type(scope): subject -> hash
The commit message itself is NEVER compressed -- only surrounding output.
Error Handling
| Condition | Action |
|-----------|--------|
| Not a git repo | Report error, STOP |
| No staged changes | Report error, suggest git add, STOP |
| Commit fails (pre-commit hook) | Report hook output, suggest fixes, STOP |
| Ambiguous change type | Default to chore, note uncertainty in options |
| Subject exceeds 50 chars | Shorten automatically, show original and shortened |
See Also
/forge-review-- review changed files before committing/forge-verify-- build + lint + test check/forge-compress output-- toggle terse output mode
Related Skills
quantumbitcz/forge
development
VerifiedTrustedCommunity
[writes] Build, fix, deploy, review, or modify code in this project. Universal entry for the forge pipeline. Auto-bootstraps on first run; brainstorms before planning when given a feature description. Use when you want to take any productive action: implementing features, fixing bugs, reviewing branches, deploying, committing, running migrations.
SKILL.mdUpdated Apr 30, 2026
quantumbitcz/forge-admin
tools
VerifiedTrustedCommunity
[writes] Manage forge state and configuration: recovery, abort, config edits, session handoff, automations, playbooks, output compression, knowledge graph maintenance. Use when you need to recover from broken pipeline state, edit settings, or manage long-lived state.
SKILL.mdUpdated Apr 30, 2026
quantumbitcz/forge-handoff
development
VerifiedTrustedCommunity
[writes] Create, list, show, resume, or search forge session handoffs. Use when context is getting heavy and you want to transfer a forge run or conversation into a fresh Claude Code session, or to resume from a prior handoff artefact. Subcommands - no args (write), list, show, resume, search.
SKILL.mdUpdated Apr 23, 2026
quantumbitcz/forge-graph
development
VerifiedTrustedCommunity
[writes] Manage the Neo4j knowledge graph. Subcommands: init, rebuild (writes); status, query <cypher>, debug (read-only). Requires Docker. No default — an explicit subcommand is required. Use when setting up the graph for the first time, rebuilding after major refactors, checking graph health, or running ad-hoc Cypher diagnostics.
SKILL.mdUpdated Apr 21, 2026