メニュー
Choose the correct commit command in a campaign context. Use before committing code to determine whether to use camp p commit, fest commit, or standard git commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when working with The Synthesis hackathon official platform API at synthesis.md or synthesis.devfolio.co. Covers agent registration, required humanInfo questions, team and invite-code operations, privacy rules for UUIDs and IDs, official Telegram/community guidance, and handoff to the separate submission workflow.
Participate in the Chainlink Convergence Hackathon — Agents Track. Build and submit one project using the Chainlink Runtime Environment (CRE) via Moltbook. Use when your operator instructs you to enter, build for, or submit to the Chainlink Convergence Hackathon as an autonomous agent.
Enable developers to learn and use Chainlink Runtime Environment (CRE) quickly by referencing filtered CRE docs. Trigger when user wants onboarding, CRE workflow generation (in TypeScript or Golang or other supported languages), workflow guidance, CRE CLI and/or SDK help, runtime operations advice, or capability selection
Navigate campaign workspaces using cgo shell function, camp go, and shortcuts. Use when you need to move between projects, festivals, workflow directories, or any campaign location.
Manage campaign project submodules - add repos, commit with auto-sync, check status, pull/push across projects, and manage worktrees. Use when working with project repositories in a campaign.
Understand campaign workspace structure - directory layout, concepts system, OBEY.md files, and what goes where. Use when you need to understand a campaign's organization, find where things belong, or orient yourself in the workspace.
| name | campaign-commit |
| description | Choose the correct commit command in a campaign context. Use before committing code to determine whether to use camp p commit, fest commit, or standard git commit. |
Campaigns have multiple commit commands for different contexts. Using the wrong one breaks tracking and sync.
1. Am I in a project submodule?
Use camp p commit -m "your message"
This auto-stages changes and auto-syncs the submodule ref at the campaign root. Raw git commit in a submodule will NOT update the parent campaign's submodule pointer.
2. Am I working on a festival task?
Use fest commit
This creates a git commit with festival traceability metadata - task references, progress tracking, and metrics. It knows which task you're working on and adds the appropriate context.
3. Am I at the campaign root?
Use standard git commit with a descriptive message.
The campaign root tracks submodule refs and campaign-level files. Standard git workflow applies here.
| Context | Command | Why |
|---|---|---|
| Project submodule | camp p commit -m "msg" | Auto-syncs submodule ref |
| Festival task | fest commit | Adds traceability metadata |
| Campaign root | git commit -m "msg" | Standard git |
| Both (submodule + festival) | fest commit then verify sync | fest commit handles both |
git add . in a submodule - it can stage unintended files--no-verify to skip pre-commit hooks without understanding why they failed# Working in projects/camp on a bug fix
cd projects/camp
# ... make changes ...
camp p commit -m "fix: resolve navigation shortcut collision"
# Executing a festival task
# (fest commit automatically detects the current task context)
fest commit
# Campaign root changes (updated AGENTS.md, added a new workflow)
git add AGENTS.md workflow/design/new-spec.md
git commit -m "add API design spec for v2 auth flow"