npx skills add https://github.com/samhvw8/dotfiles --skill code-quality通过评审、重构和调试,结合验证关卡,实现系统性的代码改进。
| 需求 | 模块 | 参考 |
|---|---|---|
| 接收反馈 | 评审 | references/code-review-reception.md |
| 请求评审 | 评审 | references/requesting-code-review.md |
| 在声明前验证 | 评审 | references/verification-before-completion.md |
| 降低复杂度 | 重构 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
references/oop-refactoring-catalog.md| 函数式模式 | 重构 | references/functional-refactoring-patterns.md |
| 发现代码异味 | 重构 | references/code-smells-reference.md |
| 测试策略 | 重构 | references/testing-strategies.md |
| 调查缺陷 | 调试 | references/systematic-debugging.md |
| 追踪根本原因 | 调试 | references/root-cause-tracing.md |
| 添加验证 | 调试 | references/defense-in-depth.md |
| 验证修复 | 调试 | references/verification.md |
YAGNI, KISS, DRY - 始终遵循这些原则。
诚实、直接、切中要害、简洁。
技术正确性高于社交舒适度。 实施前先验证。假设前先提问。声明前先提供证据。
模式: 阅读 → 理解 → 验证 → 评估 → 回应 → 实施
规则:
grep 查找使用情况来源:
时机: 主要功能完成后、合并前、复杂修复后
流程:
BASE_SHA=$(git rev-parse HEAD~1),HEAD_SHA=$(git rev-parse HEAD)铁律: 没有最新的验证证据,不得声明完成
关卡: 识别 → 运行 → 阅读 → 验证 → 然后声明
跳过任何一步 = 说谎,而非验证。
不懈地简化。严格地保留行为。度量一切。
每次重构:小而安全,立即测试,可度量地更好。
面向对象: 提取方法,内联,用查询替换临时变量,卫语句 函数式: Map/Filter/Reduce,纯函数,组合,不可变性
没有先进行根本原因调查,就没有修复
随机修复浪费时间并制造新缺陷。
1. 系统性调试 (references/systematic-debugging.md)
2. 根本原因追踪 (references/root-cause-tracing.md) 通过调用栈向后追踪,找到原始触发点。
3. 纵深防御 (references/defense-in-depth.md) 在每一层进行验证:入口 → 业务逻辑 → 环境 → 调试
4. 验证 (references/verification.md) 运行命令。阅读输出。然后声明结果。
Bug → systematic-debugging.md (Phase 1-4)
Error deep in stack? → root-cause-tracing.md
Found root cause? → defense-in-depth.md
About to claim success? → verification.md
如果出现以下想法,请停止:
references/code-review-reception.md - 响应协议references/requesting-code-review.md - 请求流程references/verification-before-completion.md - 验证关卡references/oop-refactoring-catalog.md - Martin Fowler 的模式references/functional-refactoring-patterns.md - 函数式编程转换references/code-smells-reference.md - 23 种异味,5 个类别references/testing-strategies.md - 特征化测试,TDDreferences/systematic-debugging.md - 四阶段框架references/root-cause-tracing.md - 调用栈分析references/defense-in-depth.md - 多层验证references/verification.md - 验证协议验证。提问。然后实施。证据。然后声明。
每周安装数
171
仓库
GitHub 星标数
12
首次出现
2026年1月24日
安全审计
安装于
opencode155
codex147
gemini-cli145
cursor145
claude-code133
github-copilot132
Systematic code improvement through review, refactoring, and debugging with verification gates.
| Need | Module | Reference |
|---|---|---|
| Receive Feedback | Review | references/code-review-reception.md |
| Request Review | Review | references/requesting-code-review.md |
| Verify Before Claim | Review | references/verification-before-completion.md |
| Reduce Complexity | Refactoring | references/oop-refactoring-catalog.md |
| Functional Patterns | Refactoring | references/functional-refactoring-patterns.md |
| Find Code Smells | Refactoring | references/code-smells-reference.md |
| Test Strategies | Refactoring | references/testing-strategies.md |
| Investigate Bugs | Debugging | references/systematic-debugging.md |
| Trace Root Cause | Debugging | references/root-cause-tracing.md |
| Add Validation | Debugging | references/defense-in-depth.md |
| Verify Fix | Debugging | references/verification.md |
YAGNI, KISS, DRY - Always honor these.
Be honest, be brutal, straight to the point, and be concise.
Technical correctness over social comfort. Verify before implementing. Ask before assuming. Evidence before claims.
Pattern: READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT
Rules:
Sources:
When: After major features, before merge, after complex fixes
Process:
BASE_SHA=$(git rev-parse HEAD~1), HEAD_SHA=$(git rev-parse HEAD)Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
Gate: IDENTIFY → RUN → READ → VERIFY → THEN claim
Skip any step = lying, not verifying.
Simplify relentlessly. Preserve behavior religiously. Measure everything.
Every refactoring: small and safe, tested immediately, measurably better.
OOP: Extract Method, Inline, Replace Temp with Query, Guard Clauses Functional: Map/Filter/Reduce, Pure Functions, Composition, Immutability
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Random fixes waste time and create new bugs.
1. Systematic Debugging (references/systematic-debugging.md)
2. Root Cause Tracing (references/root-cause-tracing.md) Trace backward through call stack to find original trigger.
3. Defense-in-Depth (references/defense-in-depth.md) Validate at every layer: Entry → Business logic → Environment → Debug
4. Verification (references/verification.md) Run command. Read output. Then claim result.
Bug → systematic-debugging.md (Phase 1-4)
Error deep in stack? → root-cause-tracing.md
Found root cause? → defense-in-depth.md
About to claim success? → verification.md
Stop if thinking:
references/code-review-reception.md - Response protocolsreferences/requesting-code-review.md - Request processreferences/verification-before-completion.md - Verification gatesreferences/oop-refactoring-catalog.md - Martin Fowler's patternsreferences/functional-refactoring-patterns.md - FP transformationsreferences/code-smells-reference.md - 23 smells, 5 categoriesreferences/testing-strategies.md - Characterization tests, TDDreferences/systematic-debugging.md - Four-phase frameworkreferences/root-cause-tracing.md - Call stack analysisreferences/defense-in-depth.md - Multi-layer validationreferences/verification.md - Verification protocolsVerify. Question. Then implement. Evidence. Then claim.
Weekly Installs
171
Repository
GitHub Stars
12
First Seen
Jan 24, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode155
codex147
gemini-cli145
cursor145
claude-code133
github-copilot132
Flutter/Dart代码审查最佳实践:提升应用性能与质量的完整检查清单
945 周安装
Components.build 规范:构建现代化、可组合、无障碍 React UI 组件库的完整指南
115 周安装
Better Auth集成指南:Next.js身份验证处理器配置与Cookie处理方案
117 周安装
Google Drive 集成工具:命令行读写、搜索、文件管理,支持 OAuth 身份验证
116 周安装
NetSuite ERP集成指南:使用Membrane CLI管理客户、订单与财务
70 周安装
微信公众号文章创作助手 - 智能AI写作工具,一键生成专业公众号文案
115 周安装
现代C++开发指南:C++17/20标准、内存管理、高性能编程与最佳实践
117 周安装