메뉴
Create a PR following ICN conventions with invariants checklist, proper commit format, and change routing verification
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
ICN development companion for the InterCooperative Network Rust monorepo. Use when working on ICN code, docs, deployment, or protocol design. Provides crate-aware routing to specialist agents (icn-architect, icn-economist, icn-ops), enforces project conventions, and understands the current sprint state, cluster topology, and demo flow status. Triggers on: any ICN crate names, "cooperative contract", "mutual credit", "governance", "gossip", "K3s", "icn-dev", "ops/mcp", "Sprint", "demo flow", "CCL", "federation", "DID", "ledger", "trust graph", "icnd", "icnctl".
Full sprint-batch or stacked-PR integration pipeline. Owns merge order, rebases, local gates, and main sync.
Full sprint-batch or stacked-PR integration pipeline. Owns merge order, rebases, local gates, and main sync.
Show full ICN development status dashboard — active sessions, sprint tasks, worktree freshness, CI state, and cluster health
ICN session preflight. This skill should be used when the user explicitly invokes "/icn-agent-pack:preflight", or asks to "run preflight", "orient me on ICN", or "check the ICN session environment". Loads canonical docs and the latest handoff, then verifies branch, gh auth, ports, toolchain, and a light cargo check. Read-only; reports, never fixes.
ICN repo navigator / knowledge graph. This skill should be used when the user explicitly invokes "/icn-agent-pack:navigator", or asks to "map the repo", "build/refresh the knowledge graph", "trace this concept to its source", or "show the conceptual map / impact map". Begins the living repository knowledge-graph and conceptual-map workflow, grounded in the icn-ops MCP tools and (future) generated graph artifacts.
SOC 직업 분류 기준
| name | pr-create |
| description | Create a PR following ICN conventions with invariants checklist, proper commit format, and change routing verification |
| argument-hint | [base-branch] |
| user-invocable | true |
| allowed-tools | Bash, Read, Grep, Glob |
| truth_contract | {"canonical_sources":["ops/state/truth/policy.json","ops/state/config/repo-map.json"],"live_load_required":["git branch --show-current","git diff --name-only $(git merge-base HEAD origin/main)..HEAD"],"examples_only":[],"never_hardcode":["branch name","base branch (always confirm with git)","required check list"]} |
Create a pull request following ICN conventions.
Run these in parallel:
git status (untracked files)git diff --stat origin/main...HEAD (change summary)git log --oneline origin/main..HEAD (commits on branch)git diff origin/main...HEAD (full diff)Before creating the PR, run the appropriate checks based on changed files (follow /verify routing). If checks fail, fix issues first.
Determine the type: feat, fix, refactor, docs, test, chore, ci
Determine the scope from ICN scopes: core, identity, trust, net, gossip, ledger, ccl, governance, compute, gateway, rpc, store, obs, federation, privacy, security, crypto, sdk, web, deploy
Use gh pr create with this body structure:
## Summary
<1-2 sentence description>
## Changes
- <bullet list of changes>
## Motivation
<why this change is needed>
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing: <describe>
## Invariants
- [ ] No panics introduced in protocol paths
- [ ] Determinism preserved
- [ ] Canonical encodings unchanged (or versioned)
- [ ] Trust gates not weakened
- [ ] Kernel/app boundaries respected
## Verification
### 5. Commit message format
Title: `<type>(<scope>): <description>` (under 70 chars)
### Important
- Base branch defaults to `main` unless `$ARGUMENTS` specifies otherwise
- Push the branch with `-u` flag before creating PR
- Include `Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>` in commits
- Never create PRs without running verification first