القائمة
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.
التثبيت باستخدام 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.
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.
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 | camp-projects |
| description | 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. |
Projects are git submodules managed by camp. The key command is camp p commit which keeps submodule refs in sync automatically.
camp project add <git-url> # Add a repo as a project submodule
camp project add <url> --name foo # Add with custom name
camp project list # List all projects
camp project remove <name> # Remove a project submodule
Projects live under projects/ in the campaign root.
Always use camp p commit instead of raw git commit when working in project submodules.
camp p commit -m "fix: resolve auth bug"
This command:
-a by default)--sync by default)This saves a manual step and keeps the campaign root in sync with the project's HEAD.
Raw git commit in a submodule creates the commit but does NOT update the submodule ref in the parent campaign. This causes the campaign root to show the submodule as "dirty" and other developers will clone an older version of your project.
camp status # Git status for current project
camp status all # Git status across ALL projects
camp status all --view # TUI view of all project statuses
camp pull # Pull current project
camp pull all # Pull all projects
camp push # Push current project
camp push all # Push all projects
Git worktrees let you work on multiple branches simultaneously without switching:
camp project worktree add <project> <branch> # Create worktree
camp project worktree list # List all worktrees
camp project worktree remove <path> # Remove worktree
Worktrees live under projects/worktrees/.
git add . && git commit in a submodule - breaks submodule ref sync. Always use camp p commit.camp pull all before starting work - may miss upstream changes in other projectsgit worktree add - camp won't track them. Use camp project worktree add.