pr-self-review
Skill2 starsChanged 7 months agoMITView on GitHub
对本次 PR 改动执行结构化自检,覆盖代码质量、规范符合性、安全、测试四个维度,输出通过/失败逐项清单
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Altinity/clickhouse-sink-connectortheir own version, first seen Oct 17, 2026
- petekp/claude-code-setuptheir own version, first seen Sep 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Altinity/clickhouse-sink-connector★ 353same name
- petekp/claude-code-setup★ 48same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- advise-tech-stackSkill
- commit-with-affectsSkill
- db-dev-guideSkill
- export-db-indexesSkill
- frontend-dev-guideSkill
- frontend-ux-evaluatorSkill
- generate-pr-descriptionSkill
- generate-test-from-impactSkill
- generate-test-skeletonSkill
- lock-global-conventionsSkill
- plan-component-hierarchySkill
- plan-page-mapSkill
- proposal-reviewSkill
- propose-workflow-improvementsSkill
- record-decisionSkill
- review-guardrailsSkill
- run-pending-specsSkill
- run-testsSkill
- scan-bundle-bloatSkill
- scan-code-hygieneSkill
- scan-dead-routesSkill
- scan-frontend-qualitySkill
- scan-orphan-componentsSkill
- scan-unused-exportsSkill
- sync-llm-contextSkill
- verify-specSkill
The file
Files
PR Self-Review Skill
单独调用:
/pr-self-review在工作流中调用:由pr-review工作流 Step 2 自动触发
执行步骤
Step 1:获取变更文件清单
git diff main...HEAD --name-onlyStep 2:逐维度自检
代码质量(搜索验证):
grep -rn "console\.log\|TODO\|FIXME\|HACK" 变更文件列表
grep -rn "localhost:\|127\.0\.0\.1\|硬编码域名" 变更文件列表规范符合性(条件执行):
- 有数据库文件变更 → 读取
db-dev-guideskill(.agents/skills/db-dev-guide/SKILL.md)并逐条验证 - 有前端文件变更 → 检查 Tailwind 物理色、裸 hex(若 css_framework=tailwind)
- 有 commit message → 验证格式是否符合
commit-with-affects规范
安全(搜索验证):
grep -rn "f\".*{.*}\|f'.*{.*}'\|%s.*%" 变更文件 # Python SQL 拼接风险
grep -rn "\.query\(.*\+\|\.execute\(.*\+" 变更文件 # SQL 拼接风险测试:
- 检查新增的业务文件是否有对应的测试文件
- 检查测试文件中是否有断言(非空测试)
Step 3:输出结构化结果
输出格式
## PR 自检报告
### 代码质量
- [x] 无 console.log 调试语句
- [x] 无硬编码地址
- [ ] ⚠️ 发现 TODO 注释:backend/app/service.py:45 — 建议处理或转为 issue
### 规范符合性
- [x] 数据库变更符合 db.md 规范
- [x] 前端无 Tailwind 物理色
- [x] Commit message 格式正确
### 安全
- [x] 无 SQL 拼接
- [ ] ⚠️ 需人工确认:新增 API /api/admin/xxx 是否有权限校验
### 测试
- [x] 新增 Service 有对应测试文件
- [ ] ⚠️ src/services/NewFeature.ts 无对应测试文件,请说明原因
---
自检完成:3 项通过,3 项需关注(标注 ⚠️)约束
- MUST 每一项检查都通过工具验证(grep / 文件读取),不凭感觉判断
- NEVER 将"需人工确认"项标为通过
- 输出的 ⚠️ 项必须给出具体文件路径和行号(便于定位)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

