メニュー
Git branching strategy and commit conventions for syspilot. Development branch with feature branches, main = releases only. Who may create/commit to which branches. USE FOR: any git operation, branch creation, committing, pushing, merging.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | syspilot.branching |
| description | Git branching strategy and commit conventions for syspilot. Development branch with feature branches, main = releases only. Who may create/commit to which branches. USE FOR: any git operation, branch creation, committing, pushing, merging. |
Implements: SYSP_SPEC_SKILL_BRANCHING_STRATEGY, SYSP_SPEC_SKILL_BRANCHING_PERMISSIONS, SYSP_SPEC_SKILL_BRANCHING_COMMIT_CONVENTIONS Requirements: SYSP_REQ_SKILL_BRANCHING_CHAINED, SYSP_REQ_SKILL_BRANCHING_MAIN_PROTECTION, SYSP_REQ_SKILL_BRANCHING_NAMING
ONLY @syspilot.release may commit to, merge to, or push to main. No exceptions.
If you are on main and need to make any change, create feature/<name> first.
Main always equals the latest release — any non-release commit on main is a violation.
syspilot uses a permanent development integration branch with short-lived feature branches:
gitGraph
commit id: "v0.2.3" tag: "v0.2.3"
branch development
checkout development
commit id: "dev-start"
branch feature/CR7
checkout feature/CR7
commit id: "CR7: specs"
commit id: "CR7: implement"
commit id: "CR7: verify"
checkout development
merge feature/CR7 id: "squash CR7"
branch feature/CR8
checkout feature/CR8
commit id: "CR8: specs"
commit id: "CR8: implement"
commit id: "CR8: verify"
checkout development
merge feature/CR8 id: "squash CR8"
checkout main
merge development id: "v0.2.4" tag: "v0.2.4"
Workflow Sequence:
@syspilot.design creates feature/<name> from development@syspilot.implement commits code on the same branch@syspilot.verify commits validation report on the same branch@syspilot.docu commits documentation updates on the same branchdevelopment@syspilot.release prepares on development (archive, version bump, release notes, validate, commit+push), then squash-merges development into main, tags, and back-merges main into developmentKey Properties:
development as integration target — all features merge heredevelopment and mainv{version} tags mark published releasesgit checkout development && git merge main prevents conflicts on next release-X theirs (development wins)| Agent | May create | May commit to |
|---|---|---|
@syspilot.release | (none) | main (squash merge from development + tag); development (prep + back-merge) |
@syspilot.design | feature/<name> | feature/<name> (the branch it created) |
@syspilot.setup | update/v{version} | update/v{version} (the branch it created) |
@syspilot.implement | (none) | current feature branch |
@syspilot.verify | (none) | current feature branch |
@syspilot.docu | (none) | current feature branch |
| All other engineers | (none) | current feature branch |
development is a permanent branch that all feature branches merge into. No agent creates development — it exists permanently.
| Pattern | Created by | Purpose |
|---|---|---|
development | (permanent) | Integration branch, all features merge here |
feature/<name> | @syspilot.design | Feature work, fixes, refactors |
update/v{version} | @syspilot.setup | Framework update branches |
main | (protected) | Release-only, always latest release |
Format: <type>: <short description>
| Type | When to use | Example |
|---|---|---|
feat | New feature or specification | feat: add branching skill RST specs |
fix | Bug fix or correction | fix: correct traceability link in REQ_123 |
docs | Documentation changes (non-spec) | docs: update PM context with CR5 status |
chore | Maintenance, cleanup, tooling | chore: archive v0.2.2 change documents |
refactor | Restructuring without behavior change | refactor: reorganize index.rst toctrees |
Rules:
main — only @syspilot.release may. No exceptions.How managers invoke engineers as subagents. 'Invoke' in any syspilot agent doc means runSubagent(). The agents: list in YAML frontmatter declares which agents can be called. Managers orchestrate — engineers execute and return structured results. USE FOR: understanding agent communication, runSubagent() calls, agents: frontmatter semantics.
Impact analysis using sphinx-needs dependency trees. Discovers affected specification elements by traversing traceability links. USE FOR: change scoping, blast radius analysis, element discovery before spec writing.
Session-to-Session (S2S) messaging for Copilot CLI agents. Use this skill whenever you need to send a message to another agent session, check your inbox, receive a pending message, or list active sessions. Triggers include: "send to session", "check inbox", "receive message", "message agent", "notify session", "S2S", "session-to-session", or any request to communicate with another named Copilot CLI session.