By ealt
Structured approaches to debugging, root cause analysis, and systematic problem-solving.
Claude Code plugin marketplace.
/plugin marketplace add ealt/claude-plugins
Tools for learning from sessions and codifying lessons into durable mechanisms — conventions, guardrails, and knowledge artifacts.
Version: 1.0.0 | License: MIT
/plugin install codification@ealt-plugins
Skills:
codifycodification-referencedebriefReview workflows for improving code and artifact quality through autonomous iterative feedback.
Version: 1.0.0 | License: MIT
/plugin install quality@ealt-plugins
Skills:
codex-reviewStructured approaches to debugging, root cause analysis, and systematic problem-solving.
Version: 1.0.0 | License: MIT
/plugin install diagnostics@ealt-plugins
Skills:
structured-debugBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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 claimReview workflows for improving code and artifact quality through autonomous iterative feedback.
Tools for learning from sessions and codifying lessons into durable mechanisms — conventions, guardrails, and knowledge artifacts.
npx claudepluginhub ealt/claude-plugins --plugin diagnosticsSystematic debugging, root cause analysis, log analysis, profiling, binary search debugging, and postmortem analysis.
專業的問題分析專家系統,提供五個專門代理(問題分析、程式碼調查、根本原因定位、Git歷史分析、日誌分析)進行系統化的深度問題診斷,支援條件觸發和並行執行
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.
Systematically debug issues with step-by-step troubleshooting approaches.
Systematic debugging and root cause analysis framework - four-phase investigation process ensuring understanding before 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.