一键导入
pr-description
Generates a PR description from the current branch diff and project conventions. Output is a ready-to-use markdown body.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generates a PR description from the current branch diff and project conventions. Output is a ready-to-use markdown body.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generates a context-specific audit brief and executes review via code-reviewer agent. Usable standalone or as a building block within other skills.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Full SDLC workflow - from task to PR. Plans, audits adversarially, implements, runs quality gates, and opens a PR.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Validates project.yaml is well-formed. Checks required fields, valid values, resolvable paths, and detects typos.
Validates code against all project architecture conventions. Reads project.yaml to determine applicable checks and runs them. Replaces individual check-* skills.
| name | pr-description |
| description | Generates a PR description from the current branch diff and project conventions. Output is a ready-to-use markdown body. |
Generates a pull request body from the current branch changes.
git log --oneline main..HEAD
git diff --stat main...HEAD
git diff main...HEAD
Read the project's instructions file for conventions and PR expectations.
Group changes by area:
Output a fenced markdown block with this structure:
## Summary
1-3 bullet points. What changed and why.
## Changes
Group by area (not by file). Each group gets 1-2 lines:
- **Domain**: added X entity, updated Y validation
- **Adapters**: new SQS consumer for Z
- **Tests**: unit + integration coverage for the above
rule://writing-style for tone/format.