Menu
Create a conventional commit from staged changes — picks type, scope, and writes the message.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Prepare a code branch and pull/merge request for human review through safe rebasing, repository-specific validation, multiple independent subagent review rounds, evidence-based fixes, conventional commits, pushing, PR creation, and CI babysitting. Use when asked to prepare, polish, or finalize a PR/MR; obtain several reviews; iterate until clean; or make a branch ready for human review.
Debug an `imprint teach` run — env vars, CLI flags, log files, tracing, and diagnostic commands. Helps diagnose slow, stuck, or failing teach runs.
Refresh checked-in examples from generated Imprint site tools and cut an Imprint patch release. Use when the user asks to commit new generated tools to examples, replace stale example tool snapshots, update example docs/tests after generated tool repairs, or publish a patch release after example/runtime fixes.
Audit and repair generated Google Flights Imprint tools. Use when validating Google Flights search, calendar, booking, airline/bag filters, one-way, round-trip, multi-city, or open-jaw behavior; when investigating `selection_token` or `selected_flights` producer-consumer contracts; or when live audit results are slow, bot-sensitive, under-tested, or incorrectly waived as infrastructure.
Investigate a site's auth-tool compile — ongoing or completed. Locate the real agent transcript (not just the hook log), read the live 2FA verification, inspect the emitted workflow.json, confirm the login actually completed, and diagnose "no auth tool compiled".
Cut a new semver release — bumps package.json, previews changelog, commits, tags, pushes, and verifies npm publish.
| name | commit |
| version | 1.0.0 |
| description | Create a conventional commit from staged changes — picks type, scope, and writes the message. |
| triggers | ["commit","conventional commit"] |
| allowed-tools | ["Bash","Read"] |
Create a well-formed conventional commit from the currently staged changes.
Run git diff --cached --stat to see what's staged. If nothing is staged, tell the user and stop.
Run git diff --cached to read the actual diff.
Pick the type based on the nature of the change:
| Type | When to use |
|---|---|
feat | New user-facing feature or capability |
fix | Bug fix |
refactor | Code restructuring without behavior change |
perf | Performance improvement |
test | Adding or updating tests |
docs | Documentation only |
ci | CI/CD configuration |
chore | Maintenance, dependencies, tooling |
build | Build system or external dependency changes |
style | Formatting, whitespace, linting (no logic) |
Pick a scope from the file paths changed. Established scopes in this repo:
cli, probe, backend, playbook, stealth-fetch, cron, notify, utils, types, replay-backend, mcp, record, redact, session-writer
If the change spans multiple areas, omit the scope. If it's a new area, derive the scope from the directory name.
Format: <type>(<scope>): <subject>
Rules:
BREAKING CHANGE: <description> if applicableShow the proposed commit message to the user. Ask if they want to proceed, edit, or cancel.
Run the commit using a heredoc:
git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"