How do I install the Campaign Commit skill?

Run npx skillmds@latest add obedience-corp/campaign-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Campaign Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Campaign Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Campaign Commit free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Campaign Commit?

Obedience-Corp (@obedience-corp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Campaign Commit by obedience-corp — Agent Skill

Name: Campaign Commit
Author: Obedience-Corp

Campaign Commit

Choose the correct commit command in a camp, also called a campaign. Use when you are about to commit and need to select `camp commit`, `camp p commit`, `fest commit`, or intentional root pointer sync via `camp refs-sync`.

File contents

Camp Commit Decision

A camp was previously called a campaign; this skill applies whichever word the user uses.

Decision

Project change (submodule, linked project, or worktree): camp p commit -m "msg"
Festival task execution: fest commit -m "msg"
Camp root files: camp commit -m "msg" (stages all root-level changes; submodule refs excluded by default)
Camp root, scoped to specific paths: git add <paths> then camp commit --all=false -m "msg" (commits only what is staged)
Intentional root pointer sync: camp refs-sync [submodule...]

Festival Commits Cover the Linked Project

When a festival or sequence has a linked project, fest commit makes up to two commits even when you run it from inside the festival:

a project commit staging the project's changes, skipped when the project is clean
a camp root commit staging only festival-scoped files, the camp's .campaign/fest/ state, and the submodule pointer

So during festival execution do not run camp p commit first and fest commit after. One fest commit covers both sides. Use --no-root to skip the camp root commit.

A festival with no linked project makes the single camp root commit only.

Deferred Commit Queue

Camp defers its own bookkeeping commits so they do not hold the terminal. The queue is machine-local and disposable; git is the record.

camp jobs                       # what is queued, running, or failed
camp jobs --json                # same, for agents
camp jobs retry all             # requeue everything that failed
camp jobs drop <id>             # give up on a failed job, keeping its content
camp jobs drop --running <id>   # a stalled job, and the worker holding it
camp jobs drain                 # wait for every lane, then exit

Dropping a job never discards work: the content stays uncommitted in the working tree for the next ordinary commit. If camp jobs reports a job as stalled, a commit message writer stopped answering; --running is what ends that wait.

Rules

Never run raw git commit anywhere in a camp; staging with git add is fine.
Keep submodule commits and root pointer sync as separate, explicit actions.
Do not bypass hooks with --no-verify without clear justification.
Do not add agent co-author trailers unless explicitly requested.

---name: campaign-commitdescription: Choose the correct commit command in a camp, also called a campaign. Use when you are about to commit and need to select `camp commit`, `camp p commit`, `fest commit`, or intentional root pointer sync via `camp refs-sync`.license: Apache-2.0---# Camp Commit DecisionA camp was previously called a campaign; this skill applies whichever word the user uses.## Decision- Project change (submodule, linked project, or worktree): `camp p commit -m "msg"`- Festival task execution: `fest commit -m "msg"`- Camp root files: `camp commit -m "msg"` (stages all root-level changes; submodule refs excluded by default)- Camp root, scoped to specific paths: `git add <paths>` then `camp commit --all=false -m "msg"` (commits only what is staged)- Intentional root pointer sync: `camp refs-sync [submodule...]`## Festival Commits Cover the Linked ProjectWhen a festival or sequence has a linked project, `fest commit` makes up to twocommits even when you run it from inside the festival:- a project commit staging the project's changes, skipped when the project is clean- a camp root commit staging only festival-scoped files, the camp's `.campaign/fest/` state, and the submodule pointerSo during festival execution do not run `camp p commit` first and `fest commit`after. One `fest commit` covers both sides. Use `--no-root` to skip the camproot commit.A festival with no linked project makes the single camp root commit only.## Deferred Commit QueueCamp defers its own bookkeeping commits so they do not hold the terminal. Thequeue is machine-local and disposable; git is the record.```bashcamp jobs # what is queued, running, or failedcamp jobs --json # same, for agentscamp jobs retry all # requeue everything that failedcamp jobs drop <id> # give up on a failed job, keeping its contentcamp jobs drop --running <id> # a stalled job, and the worker holding itcamp jobs drain # wait for every lane, then exit```Dropping a job never discards work: the content stays uncommitted in the workingtree for the next ordinary commit. If `camp jobs` reports a job as `stalled`, acommit message writer stopped answering; `--running` is what ends that wait.## Rules- Never run raw `git commit` anywhere in a camp; staging with `git add` is fine.- Keep submodule commits and root pointer sync as separate, explicit actions.- Do not bypass hooks with `--no-verify` without clear justification.- Do not add agent co-author trailers unless explicitly requested.

Frequently asked questions