Skip to content
Skills Library
Programming · Tool integration

campaign-commit

/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`.

Repository
festival ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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`.

Original author description

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`.

How it works

  1. Decision
  2. Festival Commits Cover the Linked Project
  3. Deferred Commit Queue
  4. Rules
Original SKILL.md headings · 54 lines, 374 words
SKILL.md preview
---
name: campaign-commit
description: 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`.
---

# 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.

```bash
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.

Versions

The database has no other skills named campaign-commit.

Identical content appears in 4 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version a2ac15a5c266 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cross-campaign
    Discover and reference other camps, projects, and files across camp boundaries. Use when the user mentions another camp or campaign by name, references work done "in another project/camp", or needs to find/copy/compare code across camps.
  • 100camp-projects
    Manage a camp's projects. Use when committing inside `projects/*`, deciding status/pull/push scope (root vs submodule vs all), or creating/removing project worktrees.
  • 100commit
    Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit".
  • 100commit
    Use when creating a git commit — the user asks to commit, or a unit of work is complete and ready to commit.
  • 96commit
    Use when writing a commit message, or before running `git commit`.
  • 100commit
    Stage named files and commit per the repo commit rules (else existing convention). Use for "commit this", "split into commits".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.