agentleFS
Sign inStart free
EmeaAppGbbEmeaAppGbb/spec2cloud/.github/skills/commit-protocol/SKILL.md

commit-protocol

Skill100 starsChanged 7 months agoMITView on GitHub

Create standardized git commits at phase and increment boundaries. Defines commit procedures, message formats, and state bundling. Use when committing after phase completion, increment delivery, or slice implementation.

  • Reads credentials

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a step or phase completes (and human gate approved, where applicable):

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Commit Protocol

At key checkpoints, create commits that bundle artifacts produced. This gives a clean, resumable history in git log.

Commit Procedure

After a step or phase completes (and human gate approved, where applicable):

1. Stage all changes:
     git add -A
2. Commit with an appropriate tag (see table below).
3. Update state.json to reflect the new state.
4. Append an entry to audit.log.
5. Commit the state update:
     git add .spec2cloud/ && git commit -m "spec2cloud: state update"

Commit Messages

EventCommit Message
Shell setup[phase-0] Shell setup complete
Product discovery[phase-1] Product discovery complete — N FRDs, N screens, N increments, tech stack resolved
Increment tests[increment] {id}/tests — test scaffolding complete
Increment contracts[increment] {id}/contracts — contracts generated
Increment slice[impl] {id}/{slice} — slice green
Increment all tests green[impl] {id} — all tests green
Increment delivered[increment] {id} — delivered
All increments complete[release] All increments delivered — product complete

Why Increment-Level Commits

Each increment is a self-contained delivery. Commits at increment boundaries mean:

  • git log --oneline --grep="\[increment\]" shows the delivery timeline
  • Each delivered increment is a revertable, deployable unit
  • Mid-increment commits at slice granularity create resumable checkpoints

Mandatory Completion Checklist

The orchestrator MUST verify ALL of the following for every commit:

  • Commit message follows the format table above (correct prefix for the phase/step)
  • .spec2cloud/state.json is included in the commit
  • .spec2cloud/audit.log is included in the commit
  • No secrets, .env files, or node_modules are staged
  • Co-authored-by trailer is present

BLOCKING: A commit without state.json and audit.log breaks resume capability. The orchestrator must include them before finalizing the commit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free