commit

What it does and when to use it

Validated commit — runs quick checks before committing. Use when ready to commit changes.

Arguments

/commit [commit message]

How it works

1. Steps

---
name: commit
description: Validated commit — runs quick checks before committing. Use when ready to commit changes.
disable-model-invocation: false
argument-hint: "[commit message]"
---

# Validated Commit

Run quick validation, then commit if clean.

## Steps

1. **Run quick validation**

```
/sdlc-core:validate --quick
```

2. **Run tests and smoke test** (if application code was changed)

```bash
# 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.

3. **If validation or tests fail**, report the issues and stop. Do NOT commit.

4. **If all checks pass**, proceed:
   - Review all changed files with `git status` and `git diff`
   - Stage the relevant files (prefer specific files over `git add -A`)
   - If `$ARGUMENTS` is 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:`

5. **Commit** using a heredoc for proper formatting:

```bash
git commit -m "$(cat <<'EOF'
<type>: <description>

<optional body>

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
```

6. **Run git status** after commit to verify success.

Versions

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 3fe23f718c92 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100git-commit
  Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
• 100git-commit
  Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
• 100commit-all
  You MUST use this when the user asks to commit all current changes at once, via /commit-all or in words ("commit everything", "commit all changes"), without giving a commit message of their own.
• 90review
  Review uncommitted changes against the project rules before committing. Use when the user asks for a review of their working tree, asks whether changes are ready to commit, or says they are about to commit.
• 100pre-commit
  Full validation gate before committing — quality checks, tests, coverage, security scan, changelog, and companion review. Use right before a commit to verify code is ready. Trigger on "pre-commit", "validate before commit", "ready to commit", "run all checks".
• 100validating-pre-commit
  Runs quality gate checks before commit or push. Use when preparing to commit, reproducing CI failures locally, or validating changes pass all checks.