菜单
Ensure ShipCode-required GitHub labels exist on the current repository using the gh CLI and the canonical definitions in packages/shared/src/github-labels.ts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Planner skill — turn a user task into a precise, atomic, verifiable ShipCodePlan
Expert in application security, OWASP Top 10, authentication, authorization, data protection, and security best practices for React, Next.js, and NestJS applications. Use when implementing authentication or authorization, reviewing code for vulnerabilities, handling sensitive data, or implementing encryption or hashing.
Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.
Validate Bun workspace configuration and detect common monorepo issues. Ensures proper workspace setup, dependency catalogs, isolated installs, and Bun 1.3+ best practices. Use when setting up a Bun monorepo, before adding workspace dependencies, auditing an existing Bun workspace, or validating package.json in CI.
Expert React/Next.js component architect specializing in creating consistent, reusable, and maintainable components for monorepo projects. Use when creating or refactoring UI components, reviewing component architecture, or setting up shared component patterns in a monorepo.
Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, debug agent behavior, or design content generation prompts.
| name | github-label-sync |
| description | Ensure ShipCode-required GitHub labels exist on the current repository using the gh CLI and the canonical definitions in packages/shared/src/github-labels.ts. |
Ensure all ShipCode-required GitHub labels exist on the current repository.
gh label list --limit 200 --json name
packages/shared/src/github-labels.ts):| Name | Color | Description |
|---|---|---|
shipcode:bug | #d73a4a | Something is broken. |
shipcode:deferred | #6e7781 | Intentionally postponed work. |
| Name | Color | Description |
|---|---|---|
shipcode:agent:claude | #1f6feb | Route this issue to Claude Code. |
shipcode:agent:codex | #2da44e | Route this issue to Codex. |
shipcode:agent:openrouter | #d97706 | Route this issue to the default OpenRouter executor. |
shipcode:agent:openrouter/auto | #0ea5e9 | Route this issue to OpenRouter auto routing. |
shipcode:agent:openrouter/free | #65a30d | Route this issue to OpenRouter free-tier routing. |
Workflow state is represented in the typed GitHub Projects v2 Status
single-select field (Backlog, In Progress, Human Review, Done, Deferred). ShipCode also
uses namespaced shipcode:pipeline:* labels for transient agent-loop sub-states
and debugging.
| Name | Color | Description |
|---|---|---|
shipcode:pipeline:queued | #6e7781 | Issue is queued for agent loop. |
shipcode:pipeline:planning | #0075ca | Agent is generating a plan. |
shipcode:pipeline:reviewing | #0075ca | Agent is reviewing the plan. |
shipcode:pipeline:revising | #0075ca | Agent is revising the plan. |
shipcode:pipeline:clarifying | #e4e669 | Agent is requesting clarification. |
shipcode:pipeline:executing | #d93f0b | Agent is executing changes. |
shipcode:pipeline:testing | #d93f0b | Agent is running tests. |
shipcode:pipeline:verifying | #d93f0b | Agent is verifying the result. |
shipcode:pipeline:shipping | #0e8a16 | Agent is opening or merging a PR. |
shipcode:pipeline:paused | #6e7781 | Pipeline is paused and can be resumed. |
shipcode:pipeline:needs_review | #d4c5f9 | Linked PR is waiting on review attention. |
shipcode:pipeline:ready_to_merge | #0e8a16 | Linked PR is approved and ready to merge. |
shipcode:pipeline:failed | #b60205 | Pipeline encountered an error. |
| Name | Color | Description |
|---|---|---|
shipcode:blocked:ci | #cf222e | Linked PR has failing CI checks and needs follow-up. |
shipcode:claim:active | #6e7781 | An external ShipCode-compatible dev loop has claimed this issue. |
Type, priority, status, complexity, and blast radius belong in native GitHub issue type or project fields when those fields are available. Do not recreate them as labels.
For each label not present in the repo, run:
gh label create "<name>" --color "<color>" --description "<description>"
The gh label create command is idempotent -- if the label already exists, it prints an "already exists" message to stderr. Catch and ignore that case.
Print a summary: how many created, how many already present, how many failed.
gh CLI authenticated with repo access.packages/shared/src/github-labels.ts -- update that file if labels change, then re-run this skill.