菜单
GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
How agents, skills, and commands work in Claude Code projects.
API error response format -- machine-readable codes, human-readable reasons, status code rules.
Language-agnostic code hygiene -- honest comments, no dead/reinvented/duplicated code, truthful names, real implementations, and scoped (never blanket) diagnostic suppressions.
Language-agnostic structural craft -- decompose on responsibility not size, prefer deep modules over shallow piles, and shape cohesion, coupling, interfaces, error contracts, and data invariants. Sibling to code-hygiene and readable-code.
Documentation writing conventions -- style, structure, tone, and quality standards.
CSS design system principles -- token usage, semantic layering, mobile-first, component isolation.
| name | github-conventions |
| description | GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments. |
| when_to_use | Using gh CLI, creating commits, posting PR/issue comments, or referencing issues by number. |
CRITICAL: #<number> auto-links to issues/PRs on GitHub. Use 1./2./3. for numbered lists and "Finding 1:"/"Item 1:" for labeled items -- never #1, #2, #3 as markers.
Feature branches: feature/<description> or feature/issue-<number>
Always check if a branch already exists for an issue before creating a new one.
For sub-issues of a larger feature, branch from the parent feature branch rather than main. Sub-issue work merges back into the parent feature branch, which eventually merges to main.
Conventional commits format: <type>: description
Types: feat:, fix:, docs:, style:, refactor:, test:, chore:
Optional scope: feat(frontend): description
Templates in .github/ISSUE_TEMPLATE/ -- read them for section structure.
bugenhancementPR template at .github/PULL_REQUEST_TEMPLATE.md -- read it for section structure.
Use Closes #<number> to link PRs to issues.
Reviews are posted as PR comments. See review-format.md for the
recommended structure -- severity buckets and the #N footgun to avoid in the summary.
Plans are posted as issue comments and saved to .claude/workspace/. See plan-format.md for the recommended structure.