By sethdford
Systematic debugging, root cause analysis, log analysis, profiling, binary search debugging, and postmortem analysis.
Using bisect/git bisect to isolate failure to exact commit or code path.
Race conditions, deadlocks, thread analysis, happens-before relationships.
Parsing logs, correlation analysis, reconstructing timeline of failures.
Detecting memory leaks through heap dumps, retention analysis, and reference tracing.
CPU/memory profiling, identifying bottlenecks, flame graphs, hotspot analysis.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Comprehensive, standards-grounded Claude Code skills for every role in the Product Development Lifecycle.
454 skills and 173 commands across 57 plugins for 8 roles.
| Role | Skills | Commands | Plugins | Standards Alignment |
|---|---|---|---|---|
| architect | 63 | 10 | 8 | TOGAF, IASA BTABoK, ISO 42010, SWEBOK v4 |
| engineer | 65 | 26 | 8 | SWEBOK v4, SFIA v9, DORA, SPACE, ISO 25010 |
| product-manager | 65 | 26 | 8 | AIPMM PmBoK, ISPMA SPMBoK, PDMA NPDP |
| tech-lead | 63 | 25 | 8 | SFIA v9, DORA/Accelerate, Team Topologies |
| security | 64 | 25 | 8 | NIST CSF 2.0, OWASP SAMM, MITRE ATT&CK, ISO 27001 |
| designer | 63 | 27 | 8 | WCAG 2.2, ISO 9241, Nielsen Heuristics |
| qa-engineer | 63 | 26 | 8 | ISTQB, ISO 25010, WCAG 2.2, IEEE 829 |
| sdlc | 8 | 8 | 1 | ISO/IEC 12207, ISO/IEC 15288 |
Every skill is built on three principles:
claude install github:sethdford/claude-skills/engineer
claude install github:sethdford/claude-skills/engineer/testing
claude install github:sethdford/claude-skills
| Plugin | Skills | Commands | Focus |
|---|---|---|---|
| system-design | 10 | 4 | Decomposition, DDD, microservices, event-driven, CQRS |
| quality-attributes | 8 | 3 | Scalability, reliability, performance, trade-off analysis |
| decision-making | 8 | 3 | ADRs, technology radar, build-vs-buy, migration strategy |
| data-architecture | 8 | 3 | Data modeling, storage selection, event sourcing, pipelines |
| infrastructure-design | 8 | 3 | Cloud architecture, deployment, DR, multi-region |
| architecture-governance | 7 | 3 | Principles, fitness functions, tech debt, compliance |
| communication | 7 | 3 | C4 diagrams, RFCs, stakeholder presentations, roadmaps |
| architect-toolkit | 7 | 3 | Katas, reviews, mentoring, anti-patterns catalog |
| Plugin | Skills | Commands | Focus |
|---|---|---|---|
| code-quality | 10 | 4 | Clean code, refactoring, SOLID, code smells |
| testing | 9 | 4 | TDD, property-based testing, test architecture |
| debugging | 8 | 3 | Systematic debugging, root cause analysis, postmortems |
| implementation-patterns | 8 | 3 | Design patterns, data structures, concurrency |
| api-development | 8 | 3 | REST, GraphQL, gRPC, API design and testing |
| devops-practices | 8 | 3 | CI/CD, containers, deployment, monitoring |
| database-engineering | 7 | 3 | Schema design, query optimization, migrations |
| engineer-toolkit | 7 | 3 | Technical writing, git workflow, incident response |
npx claudepluginhub sethdford/claude-skills --plugin engineer-debuggingQA skills for api-testing domain.
Master architecture communication: C4 models, RFCs, presentations, and documentation. Align stakeholders and explain architectural decisions.
Prioritization frameworks, roadmapping, and trade-off decision-making.
Design patterns, data structures, algorithms, concurrency patterns, functional patterns, reactive patterns, state management, and resource management.
Establish architecture governance, design fitness functions, manage tech debt, and ensure compliance. Build sustainable architecture practices.
Systematic debugging and root cause analysis framework - four-phase investigation process ensuring understanding before fixes
Debug issues systematically with root cause analysis and execution tracing
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Use when debugging, investigating root causes, designing experiments, or performing scientific analysis — enforces hypothesis-driven reasoning, evidence-first observation, causality validation, and structured output templates. Use when facing unknowns, repeated failures, or complex investigations requiring rigorous methodology.
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
專業的問題分析專家系統,提供五個專門代理(問題分析、程式碼調查、根本原因定位、Git歷史分析、日誌分析)進行系統化的深度問題診斷,支援條件觸發和並行執行