Apply hypothesis-driven debugging and root-cause analysis to software incidents, flaky tests, and regressions by enforcing evidence-first observation, causality gates, and verification rules, with controlled experimentation via an MCP registry and retrospective generation.
Use when facing unknowns, debugging without a clear cause, or making architecture decisions — enforces hypothesis-driven scientific reasoning through observation, hypothesis formulation, prediction, experiment design, and evidence-based conclusion. Use when previous attempts have failed or the problem space involves uncertainty.
Use when debugging software, investigating incidents, diagnosing flaky tests, or analyzing performance regressions — enforces structured observation recording with evidence IDs, causality validation, and verification gates to prevent correlation-causation pollution. Use when an agent might otherwise summarize or speculate instead of reporting observed evidence.
Design and run controlled experiments using the experiment-registry MCP server — domain-agnostic, pluggable, mechanically enforced. Use when you need evidence that a change actually improves behaviour.
Uses power tools
Uses Bash, Write, or Edit tools
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.
Professional workflow plugins for Claude Code — make Claude apply your project's actual linting rules, commit conventions, and testing standards, not generic defaults. Covers Python, shell, Perl, CI/CD, and AI tooling.
| Without plugins | With plugins |
|---|---|
| Claude gives generic Python advice | Claude applies Python 3.11+, Typer, Rich, httpx conventions specific to your stack |
| Claude says "done" before linters pass | holistic-linting enforces root-cause fixes before any task completes |
| Claude speculates and hallucinates | hallucination-detector blocks completion on ungrounded claims |
| Claude jumps to solutions without investigating | verification-gate forces evidence gathering before action |
| Session transcripts disappear with no learning | agentskill-kaizen mines transcripts for anti-patterns and generates skill patches |
| Commit messages are inconsistent | conventional-commits enforces feat/fix/chore format for semantic versioning |
| Claude reads source files when it should delegate | orchestrator-discipline hooks block investigation escalation at the tool level |
# Add the marketplace (one-time setup, ~10 seconds, no restart required)
/plugin marketplace add Jamie-BitFlight/claude_skills
# Install a plugin
/plugin install plugin-name@jamie-bitflight-skills
Start a new session and ask Claude to perform a task the plugin handles (for example, build a CLI with Typer after installing python3-development). Claude will apply the plugin's conventions rather than generic defaults.
Comprehensive frameworks with multiple skills, commands, and specialized agents.
npx claudepluginhub jamie-bitflight/claude_skills --plugin scientific-methodRead The Fucking Prompt — finds the strongest user reaction to an AI instruction-following failure in a chosen session, reconstructs the triggering assistant output, and renders a shareable terminal-style PNG.
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
Comprehensive Perl 5.30+ development plugin with modular skills for scripting, CPAN ecosystem, environment setup, testing, linting, and validation. Includes specialized agents for script development, code auditing, and CLI architecture.
Build FastMCP 3.x Python MCP servers — covers provider/transform architecture (including CodeMode, Tool Search, and server-level transforms), component versioning, session state, authorization (MultiAuth, PropelAuth, connection-pooled token verifiers), evaluation creation, Pydantic validation, async patterns, STDIO and HTTP transports, nginx reverse proxy deployment, background tasks, Prefab Apps UI, security patterns, client SDK usage, testing, deployment, and migration from FastMCP v2. TypeScript is a legacy reference only and is not updated for v3.
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Analyze Claude Code agent session transcripts to identify inefficiencies, anti-patterns, repeated mistakes, missing tooling opportunities, and user frustration signals for continuous improvement
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
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Systematic debugging, root cause analysis, log analysis, profiling, binary search debugging, and postmortem analysis.