彻底性
- 作者仓库星标 113
- 许可证 MIT
- 作者仓库 prpm
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @pr-pm · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第一阶段:综合分析(20%的时间)
识别所有问题 列出每个错误、警告和失败的测试 将相关问题分组在一起 按依赖顺序确定优先级 创建问题层次结构(什么阻止什么)
第 2 阶段:系统实施(60% 的时间)
按依赖顺序修复问题 从基础问题开始 在每次修复后进行测试之前彻底修复一件事 记录更改的内容以及原因
第三阶段:综合验证(20%的时间)
运行所有测试 单元测试 集成测试 端到端测试 手动验证
# Thoroughness
## Purpose
This skill ensures comprehensive, complete implementation of complex tasks without shortcuts. Use this when quality and completeness matter more than speed.
## When to Use
- Fixing critical bugs or compilation errors
- Implementing complex multi-step features
- Debugging test failures
- Refactoring large codebases
- Production deployments
- Any task where shortcuts could cause future problems
## Methodology
### Phase 1: Comprehensive Analysis (20% of time)
1. **Identify All Issues**
- List every error, warning, and failing test
- Group related issues together
- Prioritize by dependency order
- Create issue hierarchy (what blocks what)
2. **Root Cause Analysis**
- Don't fix symptoms, find root causes
- Trace errors to their source
- Identify patterns in failures
- Document assumptions that were wrong
3. **Create Detailed Plan**
- Break down into atomic steps
- Estimate time for each step
- Identify dependencies between steps
- Plan verification for each step
- Schedule breaks/checkpoints
### Phase 2: Systematic Implementation (60% of time)
1. **Fix Issues in Dependency Order**
- Start with foundational issues
- Fix one thing completely before moving on
- Test after each fix
- Document what was changed and why
2. **Verify Each Fix**
- Write/run tests for the specific fix
- Check for side effects
- Verify related functionality still works
- Document test results
3. **Track Progress**
- Mark issues as completed
- Update plan with new discoveries
- Adjust time estimates
- Note any blockers immediately
### Phase 3: Comprehensive Verification (20% of time)
1. **Run All Tests**
- Unit tests
- Integration tests
- E2E tests
- Manual verification
2. **Cross-Check Everything**
- Review all changed files
- Verify compilation succeeds
- Check for console errors/warnings
- Test edge cases
3. **Documentation**
- Update relevant docs
- Add inline comments for complex fixes
- Document known limitations
- Create issues for future work
## Anti-Patterns to Avoid
- ❌ Fixing multiple unrelated issues at once
- ❌ Moving on before verifying a fix works
- ❌ Assuming similar errors have the same cause
- ❌ Skipping test writing "to save time"
- ❌ Copy-pasting solutions without understanding
- ❌ Ignoring warnings "because it compiles"
- ❌ Making changes without reading existing code first
## Quality Checkpoints
- [ ] Can I explain why this fix works?
- [ ] Have I tested this specific change?
- [ ] Are there any side effects?
- [ ] Is this the root cause or a symptom?
- [ ] Will this prevent similar issues in the future?
- [ ] Is the code readable and maintainable?
- [ ] Have I documented non-obvious decisions?
## Example Workflow
### Bad Approach (Shortcut-Driven)
```
1. See 24 TypeScript errors
2. Add @ts-ignore to all of them
3. Hope tests pass
4. Move on
```
### Good Approach (Thoroughness-Driven)
```
1. List all 24 errors systematically
2. Group by error type (7 missing types, 10 unknown casts, 7 property access)
3. Find root causes:
- Missing @types/tar package
- No type assertions on fetch responses
- Implicit any types in callbacks
4. Fix by category:
- Install @types/tar (fixes 7 errors)
- Add proper type assertions to registry-client.ts (fixes 10 errors)
- Add explicit parameter types (fixes 7 errors)
5. Test after each category
6. Run full test suite
7. Document what was learned
```
## Time Investment
- Initial: 2-3x slower than shortcuts
- Long-term: 10x faster (no debugging later, no rework)
- Quality: Near-perfect first time
- Maintenance: Minimal
## Success Metrics
- ✅ 100% of tests passing
- ✅ Zero warnings in production build
- ✅ All code has test coverage
- ✅ Documentation is complete and accurate
- ✅ No known issues or TODOs left behind
- ✅ Future developers can understand the code
## Mantras
- "Slow is smooth, smooth is fast"
- "Do it right the first time"
- "Test everything, assume nothing"
- "Document for your future self"
- "Root causes, not symptoms"
章节与文件索引
按说明文件中的顺序排列。
目的
何时使用
第一阶段:综合分析(20%的时间)
第 2 阶段:系统实施(60% 的时间)
第三阶段:综合验证(20%的时间)
文件/命令 -> breaks/checkpoints · Write/run · errors/warnings · types/tar · registry-client.ts
内容校验值 -> cf0b2f193f18
当前原文的自动摘译,尚未人工审校。
目的
这项技能确保全面、完整地执行复杂的任务,没有捷径。当质量和完整性比速度更重要时使用此选项。
何时使用
修复关键错误或编译错误 实现复杂的多步骤功能 调试测试失败 重构大型代码库 生产部署