colinwilliams91/gaitor-orchestrator-cli / .agents/skills/checkpoint-commit
checkpoint-commit
VerifiedCreate a deliberate git checkpoint commit from staged or current working changes using a diff-based, model-written Conventional Commit message. Use when you want a clean commit boundary during intensive agentic iteration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
SKILL.md
View on GitHub---
name: checkpoint-commit
description: Create a deliberate git checkpoint commit from staged or current working changes using a diff-based, model-written Conventional Commit message. Use when you want a clean commit boundary during intensive agentic iteration.
argument-hint: "[optional intent or scope]"
disable-model-invocation: true
---
# Checkpoint Commit
Use this skill when you want a real commit, not an autosave fallback.
## Required Workflow
1. Confirm the current directory is inside a git repository.
2. Inspect `git status --short`.
3. If staged changes already exist, use them as the commit boundary.
4. If nothing is staged but the working tree is dirty, stage the current work with `git add -A` because the user explicitly invoked a commit checkpoint.
5. If there are still no changes, stop and report that there is nothing to commit.
6. Gather commit context from the staged diff:
- `git diff --cached --name-status`
- `git diff --cached --stat`
- `git diff --cached --unified=2`
- `git log --oneline -5`
7. Write the commit message from the actual diff.
8. Create the commit immediately unless the user explicitly asked for a preview only.
## Commit Message Rules
- Follow Conventional Commits.
- Choose `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`, or `ci` based on the behavioral change shown in the diff, not only file names.
- Add a scope only when it is obvious and materially helpful.
- Keep the subject line concise, imperative, and specific.
- Use the user's `$ARGUMENTS` as optional intent if it improves the message.
- Add a body only when the diff spans multiple tightly related changes and the extra context is genuinely useful.
- Do not use timestamps.
- Do not use placeholder phrases like `update files` or `misc changes`.
- Do not expose hidden reasoning or chain-of-thought.
## Guardrails
- Prefer one logical commit. If the staged diff spans unrelated concerns, stop and tell the user to split the change set.
- Do not push.
- Do not amend unless the user explicitly asks.
- If `git commit` fails, report the failure and the proposed commit message clearly.
## Output
After committing, report:
1. The final commit subject.
2. Whether a commit body was used.
3. The files included in the staged set.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |