メニュー
Use when finishing a chunk of work or when the user asks to commit or to update Cursor context. Commit and push with a clear message; optionally add or update a rule, skill, or subagent in .cursor. Execute without prompting (autonomous mode).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when making architectural decisions, adding components, or understanding how PeaPod's pieces fit together. Provides context on the protocol design, component boundaries, and data flow to help agents make correct design choices.
Use when building, testing, or verifying pea-core or the workspace. Run cargo build and cargo test for pea-core from repo root; fix compilation or test failures. Execute without asking for confirmation (autonomous mode).
Use when implementing features or fixes that correspond to .tasks checklists. Open the relevant .tasks file (e.g. 01-pea-core, 02-windows), implement unchecked items, and mark completed items with [x]. Run fully autonomously: no confirmation for build, test, commit, or push.
Use when working on Windows, Android, Linux, iOS, or macOS protocol implementations (pea-windows, pea-android, etc.). Follow the corresponding .tasks file (02–06); ensure wire format and discovery match pea-core and .tasks/07.
| name | commit-and-cursor |
| description | Use when finishing a chunk of work or when the user asks to commit or to update Cursor context. Commit and push with a clear message; optionally add or update a rule, skill, or subagent in .cursor. Execute without prompting (autonomous mode). |
Autonomous: Run git add, commit, and push without asking for confirmation. Hooks allow shell commands; do not prompt the user.
When finishing work or when the user asks to commit or refresh Cursor context:
Ensure build/tests pass if Rust or the workspace was changed: run cargo build -p pea-core and cargo test -p pea-core from the repo root (or full cargo build / cargo test if other crates were touched). Fix any failures before committing.
Stage, commit, and push with a clear, present-tense message. Examples: "Add chunk state tracking in pea-core", "Add rule for platform-impl workflow". Prefer one logical change per commit. Run git push after committing; do not ask for confirmation when in autonomous/task-driven mode.
If a new pattern or workflow emerged, add or edit a file in .cursor/rules/, .cursor/skills/<name>/SKILL.md, or .cursor/agents/<name>.md. Commit that in the same commit or a follow-up commit (e.g. "Add workflow-habits rule and document in CONTRIBUTING").
