代码质量提升指南：评审、重构与调试的系统性方法与实践

code-quality by samhvw8/dotfiles

183 周安装量

12 GitHub Stars

GitHub

安装命令

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 开发者，精准高效

联系我们

代码异味（5类）

臃肿物： 过长方法，过大类，过长参数列表
面向对象滥用者： 分支语句，临时字段
变更阻碍者： 发散式变更，霰弹式修改
可丢弃物： 重复代码，死代码，懒惰类
耦合者： 依恋情结，不恰当的亲密关系

面向对象： 提取方法，内联，用查询替换临时变量，卫语句 函数式： Map/Filter/Reduce，纯函数，组合，不可变性

没有先进行根本原因调查，就没有修复

随机修复浪费时间并制造新缺陷。

1. 系统性调试 (references/systematic-debugging.md)

阶段 1：根本原因调查
阶段 2：模式分析
阶段 3：假设检验
阶段 4：实施

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

如果出现以下想法，请停止：

"先快速修复，稍后再调查"
"试试改一下 X 看看"
"可能是 X，让我修复一下"
"现在应该可以了" / "似乎修复了"

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 - 特征化测试，TDD

references/systematic-debugging.md - 四阶段框架
references/root-cause-tracing.md - 调用栈分析
references/defense-in-depth.md - 多层验证
references/verification.md - 验证协议

评审： 技术严谨性高于社交表现
重构： 小、安全、经过测试、可度量
调试： 先找根本原因，一次性修复
始终： 证据先于声明

验证。提问。然后实施。证据。然后声明。

🇺🇸English

Code Quality

Systematic code improvement through review, refactoring, and debugging with verification gates.

Module Selection

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`

Core Principles

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.

Code Review

Receiving Feedback

Pattern: READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT

Rules:

❌ No performative agreement ("You're right!", "Great point!")
❌ No implementation before verification
✅ Restate requirement, ask questions, push back with reasoning
✅ YAGNI check: grep for usage before implementing suggestions

Sources:

Human partner → Implement after understanding
External reviewer → Verify technically before implementing

Requesting Review

When: After major features, before merge, after complex fixes

Process:

Get SHAs: BASE_SHA=$(git rev-parse HEAD~1), HEAD_SHA=$(git rev-parse HEAD)
Dispatch code-reviewer subagent with: WHAT, PLAN, SHAs, DESCRIPTION
Fix Critical immediately, Important before proceeding, note Minor

Verification Gates

Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Gate: IDENTIFY → RUN → READ → VERIFY → THEN claim

Skip any step = lying, not verifying.

Refactoring

Mindset

Simplify relentlessly. Preserve behavior religiously. Measure everything.

Every refactoring: small and safe, tested immediately, measurably better.

Protocol

Assessment - Baseline metrics, identify smells, classify debt
Safety Net - Verify test coverage, add characterization tests
Red-Green-Refactor - Write failing test, minimal pass, improve design
Pattern Application - SOLID, design patterns, functional transforms
Validation - Measure improvements, verify behavior preserved

Code Smells (5 Categories)

Bloaters: Long Method, Large Class, Long Parameter List
OO Abusers: Switch Statements, Temporary Field
Change Preventers: Divergent Change, Shotgun Surgery
Dispensables: Duplicate Code, Dead Code, Lazy Class
Couplers: Feature Envy, Inappropriate Intimacy

Quick Patterns

OOP: Extract Method, Inline, Replace Temp with Query, Guard Clauses Functional: Map/Filter/Reduce, Pure Functions, Composition, Immutability

Debugging

Core Principle

NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST

Random fixes waste time and create new bugs.

The Four Techniques

1. Systematic Debugging (references/systematic-debugging.md)

Phase 1: Root Cause Investigation
Phase 2: Pattern Analysis
Phase 3: Hypothesis Testing
Phase 4: Implementation

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.

Quick Reference

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

Red Flags

Stop if thinking:

"Quick fix for now, investigate later"
"Just try changing X and see"
"It's probably X, let me fix that"
"Should work now" / "Seems fixed"

References

Code Review

references/code-review-reception.md - Response protocols
references/requesting-code-review.md - Request process
references/verification-before-completion.md - Verification gates

Refactoring

references/oop-refactoring-catalog.md - Martin Fowler's patterns
references/functional-refactoring-patterns.md - FP transformations
references/code-smells-reference.md - 23 smells, 5 categories
references/testing-strategies.md - Characterization tests, TDD

Debugging

references/systematic-debugging.md - Four-phase framework
references/root-cause-tracing.md - Call stack analysis
references/defense-in-depth.md - Multi-layer validation
references/verification.md - Verification protocols

Bottom Line

Review: Technical rigor over social performance
Refactor: Small, safe, tested, measurable
Debug: Root cause first, fix once
Always: Evidence before claims

Verify. Question. Then implement. Evidence. Then claim.

Weekly Installs

171

Repository

samhvw8/dotfiles

GitHub Stars

First Seen

Jan 24, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode155

codex147

gemini-cli145

cursor145

claude-code133

github-copilot132

Flutter/Dart代码审查最佳实践：提升应用性能与质量的完整检查清单

945 周安装

代码质量提升指南：评审、重构与调试的系统性方法与实践

🇨🇳中文介绍

代码质量

模块选择

相关 Skills

核心原则

代码评审

接收反馈

请求评审

验证关卡

重构

心态

协议

代码异味（5类）

快速模式

调试

核心原则

四种技术

快速参考

危险信号

参考资料

代码评审

重构

调试

底线

🇺🇸English

Code Quality

Module Selection

Core Principles

Code Review

Receiving Feedback

Requesting Review

Verification Gates

Refactoring

Mindset

Protocol

Code Smells (5 Categories)

Quick Patterns

Debugging

Core Principle

The Four Techniques

Quick Reference

Red Flags

References

Code Review

Refactoring

Debugging

Bottom Line

最新 Skills