Automated Commit Pipeline

VerifiedCaution

Runs the governed commit pipeline: auto-branch, selective staging, formatting, linting, secret detection, conventional commit message, push.

Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude CodeCodex
#git#commit#pre-commit-hooks#secret-scanning#push

Recommended for

Automated summary

Runs a governed commit pipeline: auto-branching off a protected branch, selective staging, formatting and linting, secret scanning, documentation gating, conventional message composition, and push.

Strengths

  • Chains the easily forgotten steps in one flow: branching off main/master, selective staging, formatting, linting and gitleaks secret scanning.
  • Generates a conventional-commits message automatically, including work item ref trailers and spec numbers.
  • Halts explicitly on gate failures and offers a traceable risk-acceptance path that writes one DEC entry per finding.
  • Flags generated or sensitive files and avoids `git add -A` unless explicitly requested.

Limitations

  • Assumes the `.ai-engineering` toolchain (`ai-eng` CLI, Python scripts, manifest) is already present in the repo and is not portable as-is.
  • Requires external binaries (gitleaks, ruff) and fails when the environment lacks them.
  • Does not open pull requests or clean up branches; those are delegated to separate skills.
When to use it

Use it when you need to commit and push changes while honoring repo rules, hooks and secret scanning, without going through a pull request.

When not to use it

Avoid it when the goal is opening a PR, cleaning up branches, or working in a repository without the `.ai-engineering` structure.

Security analysis

Caution
Quality score82/100

The skill is a legitimate governed commit workflow with no destructive, exfiltrating, obfuscated, or safety-disabling instructions. The main risk is operational: it uses powerful tools such as git push, local scripts, and gate/risk commands, so it warrants caution rather than safe.

Findings
  • •Runs `git push origin <current-branch>`, a network write operation.
  • •Invokes local Python scripts and the `ai-eng` CLI, which can mutate repository state and gate state.
  • •No `allowed-tools` are declared even though the skill uses git, Python, network push, and local binaries (`gitleaks`, `ruff`, `ai-eng`).
How this analysis is made

Examples

Commit current work
commit my changes
Stage and ship specific files
stage these files and push this to remote — ship it
Commit with a message hint
commit my changes with the hint: add retry logic to the fetch client

name: ai-commit description: "Runs the governed commit pipeline: auto-branches from protected, stages selectively, formats and lints, scans for secrets, gates docs, composes a conventional message, pushes. Trigger for 'commit my changes', 'save my work', 'push this to remote', 'stage these files', 'ship it'. Not for opening a PR; use /ai-pr instead. Not for branch hygiene; use /ai-branch-cleanup instead." effort: cheap argument-hint: "--force|--only|[message hint]" tags: [git, commit, push, hooks, delivery] requires: bins:

  • gitleaks
  • ruff mirror_family: codex-skills generated_by: ai-eng sync canonical_source: .claude/skills/ai-commit/SKILL.md edit_policy: generated-do-not-edit

Commit Workflow

Runs the governed commit pipeline -- stage, format, lint, secret-detect, compose a conventional message, push -- honoring CLAUDE.md Don't rules (binding). Use /ai-pr when the goal is a pull request; see Quick Reference for invocation forms.

Process

0. Auto-branch from protected

If current branch is main/master: infer type (feat/, fix/, chore/, docs/, refactor/), generate slug deterministically with python3 .ai-engineering/scripts/branch_slug.py --prefix <type> (reads spec.md frontmatter), then git checkout -b <output>, report new branch.

1. Work item context (optional)

If .ai-engineering/specs/spec.md frontmatter has refs: include work item refs as commit body trailers (Refs: AB#101, AB#102, #45). Only include close_on_pr items — never features.

2. Instinct consolidation

If .ai-engineering/observations/observations.yml exists, run /ai-session-watch --review to consolidate session observations before committing.

3. Stage changes

git add <file1> <file2> selectively. Use git add -A only when explicitly requested. Exclude generated files, secrets, large binaries.

4. Run gate orchestrator

ai-eng gate run --cache-aware --json --mode=local

The orchestrator runs the 2-wave collector (Wave 1 fixers serial -> Wave 2 checkers parallel) with cache-aware lookup, emitting .ai-engineering/state/gate-findings.json (schema v1) covering every check. After Wave 1 fixers rewrite files, the orchestrator re-stages the safe S_pre & M_post intersection (spec-105 D-105-09); pass --no-auto-stage to disable, or set gates.pre_commit.auto_stage: false in the manifest.

5. Handle gate result

  • Exit 0 -- all checks PASS or auto-fixed. Continue to Commit.
  • Exit non-zero -- parse gate-findings.json, report failing checks per rule_id + severity, STOP. Fix root cause, re-stage, re-run /ai-commit. Override only when remediation is tracked elsewhere and the publish window forces it: ai-eng risk accept-all .ai-engineering/state/gate-findings.json --justification "<reason>" --spec <spec-id> --follow-up "<plan>" writes one DEC entry per finding with severity-default TTL (see .ai-engineering/reference/risk-acceptance-flow.md).

6. Confirm commit readiness

The documentation gate inside the orchestrator is mandatory.

See .ai-engineering/reference/gate-policy.md for the local fast-slice + CI authoritative split.

7. Commit

Compose message via python3 .ai-engineering/scripts/commit_compose.py --type <type> [--task X.Y] --desc "<desc>". --desc is mandatory (spec-139 M8 D-139-06) — derive it from the current plan.md task title (grep -m1 '^- \[ \] ' .ai-engineering/specs/plan.md) or from staged-files / operator hint on off-chain WIP commits. The legacy <DESC> placeholder fallback is deprecated. Doc-gate via python3 .ai-engineering/scripts/doc_gate.py --changed-paths "<staged>" (exit 1 → block; CHANGELOG.md or README.md must accompany changes under src/, tools/, .codex/skills/).

  • With active spec: feat(spec-NNN): Task X.Y -- <desc>, fix(spec-NNN): <desc>, chore(spec-NNN): <desc>.
  • Without spec: type(scope): description (conventional commits, imperative mood). Valid types: feat, fix, perf, refactor, style, docs, test, build, ci, chore, revert.
  • --force skips preview; otherwise preview and confirm.

8. Push

git push origin <current-branch>. Block if on main/master.

/commit --only

Execute the full pipeline through Commit. Skip Push.

Drift recovery

Exit 78 = stack drift. Run ai-eng doctor --fix in shell, retry. Never --no-verify.

Examples

User: "commit only the spec files and don't push yet" → /ai-commit --only .ai-engineering/specs/ stages only the named paths, runs the full pipeline (auto-branch, ruff format + lint, gitleaks scan, doc gate, conventional message) through commit, and stops before push.

Quick Reference

| Goal | Command | |------|---------| | Auto-stage, format, lint, scan, commit, push | /ai-commit | | Stage only named files | /ai-commit --only path/to/file.py | | Provide a message hint | /ai-commit "fix(auth): ..." | | Skip preview | /ai-commit --force | | Stop before push | /ai-commit --only ... |

Integration

Called by: user directly (off-chain, WIP-only flows). /ai-pr carries the same Steps 0-6 inline (single-responsibility per spec-132 T-3) — it does NOT delegate back here. Calls: git, ruff, gitleaks, ai-eng spec verify --fix. Reads: manifest.yml, CLAUDE.md. See also: /ai-pr, /ai-branch-cleanup, /ai-resolve-conflicts.

$ARGUMENTS

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/automated-commit-pipeline-mrwakflx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/automated-commit-pipeline-mrwakflx/download' --output '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md.part' && mv '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md.part' '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Quick Reference
GoalCommand
Auto-stage, format, lint, scan, commit, push/ai-commit
Stage only named files/ai-commit --only path/to/file.py
Provide a message hint/ai-commit "fix(auth): ..."
Skip preview/ai-commit --force
Stop before push/ai-commit --only ...

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md' && test -s '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ai-commit' && cp -R '.skill-downloads/automated-commit-pipeline-mrwakflx' '.claude/skills/ai-commit'

Codex
test -f '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md' && test -s '.skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ai-commit' && cp -R '.skill-downloads/automated-commit-pipeline-mrwakflx' '.agents/skills/ai-commit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/automated-commit-pipeline-mrwakflx'

openskills read 'automated-commit-pipeline-mrwakflx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/automated-commit-pipeline-mrwakflx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills