Jamie-BitFlight
- 284 skills
- 0 followers
- last month last updated
- ▌ Pypi Readme Creator 2 · jamie-bitflight bundleUse when creating a README for a Python package, preparing for PyPI publication, fixing README rendering errors found by twine check, choosing between README.md and README.rst, or configuring the readme field in pyproject.toml. Generates professional, PyPI-compliant README files.
- ▌ Python3 Add Feature 2 · jamie-bitflightGuided workflow for adding new features to Python projects. Use when planning a new feature implementation, when adding functionality with proper test coverage, or when following TDD to build features incrementally.
- ▌ Python3 Test Design 2 · jamie-bitflightUse when designing pytest test suite architecture, planning test coverage strategy, or reviewing test structure for Python 3.11+ projects. Activates on "design a test strategy", "plan test coverage", "create test architecture", or when TDD/BDD/property-based testing patterns are mentioned. Guides fixture design, parametrization, async testing, and mutation testing coverage decisions.
- ▌ Evaluate Sdlc Layers 2 · jamie-bitflightEvaluate and iterate on the SDLC Layer Separation Architecture implementation. Runs validation checks (cross-references, doc completeness, layer metadata, integration points), produces a findings report, and supports iterative fixes. Use when validating first-pass implementation, before claiming layer work is complete, or when improving layer docs/schema.
- ▌ Test Failure Mindset 3 · jamie-bitflightUse when encountering failing tests, diagnosing test errors, or establishing a systematic approach to test failure investigation. Activates on "test failure analysis", "debugging tests", or "why tests fail" requests. Establishes the mindset that treats test failures as valuable diagnostic signals requiring root-cause investigation — not automatic code fixes or test dismissal.
- ▌ Analyze Test Failures 3 · jamie-bitflightUse when analyzing failing test cases to determine whether failures indicate genuine bugs or test implementation issues. Activates on "analyze failing tests", "debug test failures", "investigate test errors", or when provided with specific failing test names or output. Applies balanced investigative reasoning — does not auto-fix tests without establishing root cause.
- ▌ Async Python Patterns 2 · jamie-bitflightUse when building async APIs, concurrent systems, or I/O-bound Python applications requiring non-blocking operations. Covers asyncio, async/await patterns, task scheduling, synchronization primitives, and high-performance concurrent programming.
- ▌ Group Items To Milestone 2 · jamie-bitflightUse when assigning backlog items to a GitHub milestone. Args: {milestone-number} [P0|P1|P2|title-filter]. Uses backlog list to load items, shows items with GitHub Issue status, lets user select which to assign. Creates missing GitHub Issues for selected P0/P1 items, assigns all to the milestone, updates Project V2 Status to Backlog. Use after create-milestone to populate a sprint or release.
- ▌ Specialist Skill Routing 2 · jamie-bitflightUse as the routing layer for Python development tasks — matches task descriptions against trigger lists and activates specialist skills before starting work. Covers Typer, Rich, Textual, FastMCP/MCP, ty type checker, uv, Hatchling, TOML editing, pre-commit/prek, async Python, PyPI packaging, complex linting, and technical debt modernization.
- ▌ Comprehensive Test Review 3 · jamie-bitflightUse when reviewing test suites for coverage, isolation, mock usage, naming conventions, or completeness. Activates on "review test coverage", "audit test quality", or "check tests for completeness" requests. Performs thorough checklist-driven review covering test isolation, mock correctness, AAA pattern adherence, and naming standards.
- ▌ Python3 Publish Release Pipeline 2 · jamie-bitflightSet up CI/CD pipeline for Python package publishing to PyPI. Use when preparing to publish a package, when setting up automated releases, or when configuring GitHub Actions or GitLab CI for Python projects.
- ▌ Review Against Solid Principles 2 · jamie-bitflightEnsemble SOLID review — fans the ruleset across overlapping focused workers over the same code, then reduces by corroboration.
- ▌ Fact Check 2 · jamie-bitflightVerify claims in backlog items, skill documentation, or plugin content against primary sources. Spawns parallel @dh:fact-checker agents using mcp__Ref, mcp__exa, mcp__context7 as primary tools — training data recall is rejected as evidence. WebFetch/WebSearch are last-resort fallbacks. Produces VERIFIED/REFUTED/INCONCLUSIVE verdicts with citations. Triggers on "fact check", "verify claims", "check against primary sources", or when backlog items are marked UNVERIFIED.
- ▌ Find Cause 2 · jamie-bitflightWrap investigation requests with evidence-chain discipline. Use when the user asks to find out why something happens, look into something, research a root cause, debug an issue, or investigate unexpected behavior. Transforms vague investigation requests into reproducible-proof investigations. Invoke with /dh:find-cause <description of what to investigate>.
- ▌ Orchestrate 2 · jamie-bitflightUse when orchestrating a Python development task via specialized agents. Activates on "build a Python CLI", "add a feature", "write tests", "refactor Python code", "debug Python", "code review", or any multi-agent Python workflow. Invoke as /orchestrate with a task description or alone to use conversation context.
- ▌ Snakepolish 2 · jamie-bitflightImplementation phase for stinkysnake workflow. Use when tests are written and plan is ready. Implements functions following the modernization plan, runs tests until passing.
- ▌ Stinkysnake 2 · jamie-bitflight bundleProgressive Python quality improvement with static analysis, type refinement, modernization planning, plan review, and test-driven implementation. Use when addressing technical debt, eliminating Any types, applying modern Python patterns, or refactoring for better design.
- ▌ Toml Python 2 · jamie-bitflightUse when reading or writing pyproject.toml or .toml config files in Python, editing TOML while preserving comments and formatting, designing configuration file formats for Python tools, working with tomlkit or tomllib, or implementing atomic config file updates.
- ▌ Modernpython 2 · jamie-bitflight bundleUse when reviewing Python code for modernization opportunities, writing new Python 3.11+ code to ensure modern patterns, or refactoring legacy code to current idioms. Covers proper types, DRY, SRP, framework patterns, and idiomatic Python improvements.
- ▌ Shebangpython 2 · jamie-bitflightValidate Python shebangs and PEP 723 inline script metadata. Use when checking if Python files have correct shebangs based on their dependency requirements, when fixing incorrect shebang patterns, or when adding PEP 723 script blocks to standalone scripts with external dependencies.
- ▌ Typer And Rich 2 · jamie-bitflight bundleUse when building Typer/Rich CLI applications or reviewing existing CLI code for correctness. Activates on requests involving Rich table rendering, console output handling, testing Rich-formatted output, or Typer command wiring. Prevents common AI mistakes — Rich table wrapping in non-TTY contexts, incorrect stderr/stdout separation, and integration pitfalls. Load alongside the typer and rich API reference skills.
- ▌ Python3 Packaging 2 · jamie-bitflightConfigure pyproject.toml and Python packaging for distribution. Use when setting up a new Python package, when configuring build tools and dependencies, or when preparing a project for PyPI publishing.
- ▌ Complete Milestone 2 · jamie-bitflightClose a completed GitHub milestone. Args: {milestone-number}. Audits open and closed issues, offers to carry forward open items to a new or existing milestone, closes the GitHub milestone, updates Project V2 Status to Done for closed issues, and generates a completion summary. Use when a sprint or release is finished and needs to be officially closed.
- ▌ Create Feature Task 2 · jamie-bitflightUse when creating a new feature task with structured tracking, phases, and documentation. Activates on "create a feature task", "set up development tracking", or "plan a feature implementation" requests. Produces a comprehensive feature development task with acceptance criteria, phase breakdown, and tracking artifacts ready for SAM pipeline execution.
- ▌ Lint 2 · jamie-bitflightUse when checking skill quality, validating frontmatter before commit, or diagnosing validator warnings. Runs the plugin validator on a skill, agent, or plugin directory — reports token complexity, broken links, frontmatter issues, and structural problems. Pass the path as an argument.
- ▌ Rtfp 2 · jamie-bitflightRead The Fucking Prompt — finds the strongest user reaction to an AI instruction-following failure in a chosen session, reconstructs what the assistant did wrong, and renders a shareable terminal-style PNG. Use when asked to find rage moments, generate a rage receipt, or capture a frustration incident from a session.
- ▌ Typer 2 · jamie-bitflight bundleUse when building CLI applications with Typer — creating commands, defining arguments and options, composing subcommands, testing with CliRunner, or using advanced features like callbacks and autocompletion. Covers app creation, parameter types, subcommand composition, testing patterns, and output utilities.
- ▌ Optimize 2 · jamie-bitflightUse when the primary outcome is refining an existing AI-facing artifact without dropping behavior, including SKILL.md, AGENTS.md, CLAUDE.md, rules, prompts, and agent definitions that need sharper invocation, structure, or completion criteria.
- ▌ Mkdocs 2 · jamie-bitflight bundleComprehensive guide for creating and managing MkDocs documentation projects with Material theme. Includes official CLI command reference with complete parameters and arguments, and mkdocs.yml configuration reference with all available settings and valid values. Use when working with MkDocs projects including site initialization, mkdocs.yml configuration, Material theme customization, plugin integration, or building static documentation sites from Markdown files.
- ▌ Textual 2 · jamie-bitflight bundleUse when building Textual TUI apps — creating widgets, laying out screens, handling events, managing reactivity, testing with Pilot, or running background workers. Covers App lifecycle, CSS styling, screen stack, reactive attributes, custom messages, actions, bindings, and the Worker API.
- ▌ Hatchling 2 · jamie-bitflight bundleUse when working with Hatchling — configuring build system setup, pyproject.toml metadata, dependencies, entry points, build hooks, version management, wheel and sdist builds, package distribution, setuptools migration, or troubleshooting Hatchling build errors. Covers PEP 517/518/621/660 standards.
- ▌ Modern Git · jamie-bitflight bundleModern Git workflows, best practices, and commands. Use when the user asks about Git branch management (git switch vs checkout), file restoration (git restore), fixup commits, autosquash rebasing, git worktrees, rerere, force-with-lease, repository cleanup (git clean, stale branches, bloat analysis), history navigation (revision syntax, range notation, pickaxe search), recommended global git config, or GitButler and the but CLI.
- ▌ Woo Sailor · jamie-bitflightOptimize processes in a file or directory by converting prose/bullet workflows to Mermaid diagrams — delegates to the process-siren:process-siren agent. Use when given a single SKILL.md, agent file, CLAUDE.md, or rules file to convert, or a directory containing any of those. Supports --dry-run or --report for read-only planning mode.
- ▌ Perl Testing · jamie-bitflight bundleThis skill should be used when the user asks to write Perl tests, test Perl code, use Test More, run prove, create test suite, mock Perl, or mentions Perl testing, TAP, Test Class, Test Deep, or test-driven development in Perl.
- ▌ Assessment Reporting · jamie-bitflight bundleFormat and score completed plugin assessment findings without starting another assessment workflow. Use when a plugin assessment needs the standard report structure, scoring criteria, severity breakdown, or marketplace-readiness result.
- ▌ Dispatch Contract · jamie-bitflightWhich agent a dh workflow dispatches, and the artifact consumer invariant.
- ▌ Subagent Contract · jamie-bitflightWhere a dispatched step puts its output, and how it signals state upstream.
- ▌ File Classification · jamie-bitflight bundleClassify changed prose files into review tiers before deciding SKIP. Use when reviewing a diff containing prose files.
- ▌ Plugin Creator Meta Docs · jamie-bitflightPlugin creator documentation index. Load when needing to read about plugin validation error codes, skill creation, agent creation, or plugin structure.
- ▌ Python CLI Architect · jamie-bitflight bundleUse when the python-cli-architect agent needs project structure reference and task completion quality gates for Python CLI projects. Loaded automatically by the python-cli-architect agent — covers package layout, Hatchling configuration, and implementation quality criteria.
- ▌ Test Failure Mindset 2 · jamie-bitflightUse when encountering failing tests, diagnosing test errors, or establishing a systematic approach to test failure investigation. Activates on "test failure analysis", "debugging tests", or "why tests fail" requests. Establishes the mindset that treats test failures as valuable diagnostic signals requiring root-cause investigation — not automatic code fixes or test dismissal.
- ▌ Analyze Test Failures 2 · jamie-bitflightUse when analyzing failing test cases to determine whether failures indicate genuine bugs or test implementation issues. Activates on "analyze failing tests", "debug test failures", "investigate test errors", or when provided with specific failing test names or output. Applies balanced investigative reasoning — does not auto-fix tests without establishing root cause.
- ▌ Review Verdict Contract · jamie-bitflight bundleLoad the shared verdict, punch-list, SKIP, and gate schema used by the dh multi-perspective review orchestrator, reviewers, and synthesizer. Use only when one of those components must produce, parse, validate, or gate review results.
- ▌ Agentskill Kaizen Meta Docs · jamie-bitflightAgentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.
- ▌ Comprehensive Test Review 2 · jamie-bitflightUse when reviewing pytest test suites for coverage, isolation, mock usage, naming conventions, or completeness. Activates on requests like "review test coverage", "audit test quality", or "check tests for completeness". Performs thorough checklist-driven review for test isolation, mock correctness, AAA pattern adherence, and naming standards.
- ▌ Meta Workflow Graph Refresh · jamie-bitflightEntry point for refreshing the DH workflow graph after changes to skills, agents, Mermaid flowcharts, MCP tools, or artifact flows. Use after any structural workflow change to keep docs/dh-workflow-graph.json current.
- ▌ Python3 Development Meta Docs · jamie-bitflightPython 3 development plugin documentation index. Load when needing to read about Python implementation patterns, task file conventions, or stdlib scripting.
- ▌ Orchestrator Discipline Meta Docs · jamie-bitflightOrchestrator discipline plugin documentation index. Load when needing to read about orchestration patterns, delegation rules, or context window management.
- ▌ Beads 2 · jamie-bitflight bundleUse when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
- ▌ Pre Commit 2 · jamie-bitflight bundleConfigures and runs git hooks with prek (or the pre-commit it replaces — same `.pre-commit-config.yaml`). Use when adding or troubleshooting git hooks, writing a `prepare-commit-msg` or `commit-msg` stage hook, or authoring `.pre-commit-hooks.yaml` for hook distribution.
- ▌ Beads · jamie-bitflight bundleUse when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
- ▌ Clear Cove Task Design · jamie-bitflightUse when orchestration or planning agents are producing task plans, task prompts, or TASK.md instructions that must be unambiguous, verifiable, and resistant to hallucination. Applies CLEAR (Concise, Logical, Explicit, Adaptive, Reflective) to structure and write agent task prompts, then adds CoVe (Chain of Verification) checks where accuracy risk is meaningful. Activates on draft task prompts, swarm plans, migration tasks, and multi-step plans requiring independently executable steps.
- ▌ Code Review Typescript · jamie-bitflightProvides TypeScript-specific code review patterns covering strict mode, ESM, type safety, branded types, discriminated unions, async patterns, runtime safety, and common anti-patterns. Activates on detection of tsconfig.json, *.ts, or *.tsx files during code review — loaded automatically by dh:code-reviewer.
- ▌ Implementation Manager · jamie-bitflight bundleManages feature implementation task state via SAM MCP tools. Use when querying task status, listing ready tasks, claiming tasks for execution, updating task timestamps, or coordinating multi-task feature rollout. Activated by the /dh:execution orchestrator to track progress — also activates directly when managing tasks or configuring hook profiles.
- ▌ Holistic Linting Resolver · jamie-bitflightLinter-specific resolution workflows for ruff, mypy, pyright, and basedpyright. Provides systematic root-cause analysis procedures, suppression gates, and verification steps. Use when resolving linting errors as a sub-agent, implementing fixes systematically, or conducting type flow analysis.
- ▌ Claude Skills Overview 2026 · jamie-bitflight bundleReference guide for Claude Code skills system (March 2026). Use when creating, modifying, or understanding skills, SKILL.md format, frontmatter fields, hooks, context fork, or skill best practices.
- ▌ Evaluate And Tighten Skills · jamie-bitflight bundleGenerate a focused behavioral contract for an existing skill, then remove instructions that do not contribute to that behavior. Use before eval testing of a skill, use when optimizing skill token usage.
- ▌ Evidence First Debugging · jamie-bitflight bundleUse 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.
- ▌ Complete Implementation · jamie-bitflight bundleUse when all tasks for a feature are marked COMPLETE — runs holistic quality gates including code review, feature verification, integration check, documentation drift audit and update, and context refinement. Creates follow-up plans when issues are found.
- ▌ Specialist Skill Routing · jamie-bitflightRoutes Python engineering tasks to specialist skills by matching trigger patterns before any architecture, plan, or code is written. Use when working with Typer CLI frameworks, Rich or Textual terminal UIs, CLI UI/UX design, questionary prompts, FastMCP/MCP servers, ty type checker, uv package manager, Hatchling build backend, TOML editing, pre-commit/prek hooks, async Python, PyPI packaging, complex linting, technical debt modernization, testing workflows, feature development, or stdlib-only scripting.
- ▌ Code Review Architecture · jamie-bitflightUse when a task asks for architecture review, dependency graph visualization, module coupling analysis, or circular dependency detection. Auto-detects scope (git diff → PR diff → full project). Reads project config (pyproject.toml, tsconfig.json, go.mod, Cargo.toml) to establish the intra-project module namespace before parsing imports. Builds a module-dependency graph across Python, TypeScript, JavaScript, Go, Rust, and Java. Detects cycles via graphify output or an executable Python script. Checks Conway's Law alignment against CODEOWNERS and directory structure. For Claude plugin repos, also traces cross-language chains: hook configs → hook scripts, SKILL.md/agent docs → node/uv-run scripts, PEP 723 inline deps, and MCP tool calls. Emits Mermaid flowcharts with severity color-coding (red = circular dep, yellow = high-coupling, green = clean, blue = Conway violation). Applies recursive semantic partitioning for graphs > 40 nodes. Registers each diagram as a codebase-analysis artifact.
- ▌ Multi Perspective Review · jamie-bitflight bundleUse when a diff needs four parallel perspective reviewers (Security, Performance, Quality, Accessibility). Creates an ephemeral SAM plan, collects structured verdicts, synthesizes them into one deduplicated cross-referenced punch list, prints one summary line per perspective, and exits non-zero if any perspective returns REJECT. SKIP is a passing outcome.
- ▌ Claude Plugins Reference 2026 · jamie-bitflight bundleComplete reference for Claude Code plugins system (April 2026). Use when creating plugins, understanding plugin.json schema, marketplace configuration, bundling skills/commands/agents/hooks/MCP/LSP/monitor servers, plugin caching, validation, or distribution. Covers plugin components, directory structure, installation scopes, environment variables, CLI commands, debugging, and enterprise features.
- ▌ Write Frontmatter Description · jamie-bitflightWrite or rewrite frontmatter description fields for Claude Code skills and agents. Use when creating new skills/agents, description exceeds 1024 characters, description uses forbidden YAML multiline indicators (>-, |-), description lacks trigger keywords, or when optimizing descriptions for AI tool selection. Ensures descriptions are single-line, complete, informative, third-person, front-loaded with trigger conditions.
- ▌ Comprehensive Test Review · jamie-bitflightPerforms checklist-driven review of pytest test suites against coverage thresholds (80% line/branch minimum, 95% for critical paths), AAA pattern adherence, pytest-mock usage, test isolation, naming clarity, type hints, and flaky pattern detection. Use when auditing test quality before a release, reviewing coverage gaps, checking tests for completeness or best practices, or validating mocking standards. Accepts a test file or directory as input and outputs prioritized findings grouped by HIGH, MEDIUM, and LOW priority.
- ▌ Code Review Claude Skills · jamie-bitflightLoaded automatically when reviewing Claude skills or agent definitions — covers SKILL.md structure, frontmatter validity, token budget, description quality, and agent contract compliance.
- ▌ Holistic Linting Orchestrator · jamie-bitflightOrchestrator delegation workflows for linting. Guides orchestrators on when and how to delegate to linting-root-cause-resolver and post-linting-architecture-reviewer agents. Use when orchestrating linting tasks, delegating quality checks, or reading linting resolution reports.
- ▌ Orchestrator Discipline · jamie-bitflight bundleOrchestrator context window discipline enforcement. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that waste context, and rationalizing delegation bypasses. Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows. Activates PreToolUse hooks that surface decision points before source file reads and diagnostic command execution.
- ▌ Subagent Refactoring Methodology · jamie-bitflightAnalysis criteria, transformation patterns, output format, and validation checklist for refactoring Claude Code agent prompt files. Load this skill when preparing to run the subagent-refactorer agent or when reviewing agent prompt files for structural, model optimization, or instruction quality improvements.
- ▌ Python Cross Platform Smoothing · jamie-bitflightUse when writing Python scripts that must run on Windows, Linux, and macOS — especially when Rich or Typer output breaks on Windows, when dealing with Unicode/encoding errors, ANSI escape handling, terminal detection, path separators, or console color support. Provides verified cross-platform patterns covering stdout/stderr encoding guards, Windows console quirks, terminal capability detection, and portable I/O for CLI, TUI (Rich/Textual), and GUI environments.
- ▌ Claude Session Data Schema Reference · jamie-bitflight bundleClaude Code session log schema — JSONL record types, message structure, tool call/result pairing, subagent file locations, team session layout, task/plan/team configuration paths. Use when parsing ~/.claude/projects/**/*.jsonl files, writing PostToolUse hooks that measure response sizes, building session analyzers, or any agent that reads or queries Claude session transcripts.
- ▌ Orchestrating Python Development · jamie-bitflightProvides agent selection criteria, workflow patterns (TDD, feature addition, code review, refactoring, debugging), quality gates, and python-cli-architect vs stdlib-scripting routing for Python engineering tasks. Activated by python-engineering:orchestrate at Step 1 before any task is routed. Also activates when an orchestrator needs to select the correct Python specialist agent or chain agents across a multi-step Python workflow.
- ▌ Python3 Publish Release Pipeline · jamie-bitflightConfigures CI/CD pipelines for automated Python package publishing to PyPI or GitLab Package Registry. Use when creating GitHub Actions or GitLab CI release workflows, setting up trusted publishing or API token-based PyPI authentication, configuring version management with git tags and hatch-vcs, writing pyproject.toml publishing metadata, testing packages against TestPyPI, or documenting the release process for a Python project.
- ▌ Standards For Python Development · jamie-bitflightShared Python 3.11+ development standards covering type safety (ty, native generics, Protocol, TypeIs), layered architecture, error handling, performance, identifier naming, UI/CLI patterns (Rich/Typer), testing requirements (pytest, 80% coverage, TDD), and quality gates. Activates when any Python skill or agent needs to apply shared standards for implementation, code review, refactoring, or test authoring.
- ▌ Review Against Solid Principles · jamie-bitflightSingle-pass SOLID review — dispatches one reviewer over the complete ruleset, emitting the fixed candidate schema.
- ▌ Test Failure Mindset · jamie-bitflightEstablishes a dual-hypothesis investigation mindset for every test failure — treating failures as diagnostic signals that may indicate a real bug OR an incorrect test, never defaulting to automatic code changes or test dismissal. Use when encountering failing tests, debugging test errors, running a test suite that shows regressions, or any request involving "test failure analysis", "why is this test failing", or "should I fix the test or the code". Loads a 5-step protocol covering failure reading, implementation tracing, requirement context, reasoned decision-making, and learning extraction. Works alongside analyze-test-failures for detailed per-failure analysis and comprehensive-test-review for full suite review.
- ▌ Python3 Development · jamie-bitflight bundleUse when building Python 3.11+ CLI apps (Typer/Rich), writing pytest test suites, fixing ruff linting or ty/mypy type errors, configuring pyproject.toml, creating portable scripts, or reviewing Python code. Activates on all Python implementation tasks — routes to specialist agents for CLI architecture, test design, packaging, and code review. Authoritative reference for modern Python 3.11-3.14 patterns and TDD workflows.
- ▌ Agent Capability Analyzer · jamie-bitflight bundleRuns the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agent behavior.
- ▌ Claude Subagent Reference · jamie-bitflight bundleReference spec and schema for Claude Code subagents — covers built-in agents (Explore, Plan, general-purpose), all frontmatter fields (name, description, tools, disallowedTools, model, permissionMode, maxTurns, skills, mcpServers, hooks, memory, background, effort, isolation, color, initialPrompt), scope and file locations, invocation patterns (@-mention, --agent, --agents CLI), tool restrictions, and example subagent definitions. Use when creating, configuring, or debugging a subagent definition file, looking up a frontmatter field, choosing between subagents and agent teams, or understanding what loads at subagent startup.
- ▌ Shared Content References · jamie-bitflight bundleStore instructional prose once and reference it from multiple skills or agents instead of duplicating it. Use when the same steps, rules, or reference material appear in two or more SKILL.md or agent files in one plugin, when deciding whether a shared doc belongs in the plugin-root docs directory or a single skill's references directory, or when tempted to use a symlink or a ../ path to share a file between components.
- ▌ Analyze Test Failures · jamie-bitflightAnalyzes failing test cases to determine whether failures indicate genuine bugs or incorrect test implementations. Use when debugging test failures, investigating test errors, classifying failures as test bugs vs implementation bugs vs ambiguous behavior, or when given specific failing test names or pytest output. Applies balanced investigative reasoning — never auto-fixes tests without establishing root cause first.
- ▌ Async Python Patterns · jamie-bitflightUse when writing asyncio Python code — async/await coroutines, concurrent I/O with asyncio.gather, task creation and cancellation, semaphore rate limiting, producer-consumer queues, async context managers, async generators, WebSocket servers, aiohttp web scraping, async database operations, run_in_executor for blocking calls, or testing async code with pytest-asyncio. Covers FastAPI and aiohttp patterns, synchronization primitives, timeout handling, and common pitfalls like event loop blocking and missing await.
- ▌ Semantic Code Search · jamie-bitflightUse when searching a codebase by behavior, intent, or natural language description rather than exact identifiers. Activates the CocoIndex Code MCP server for semantic code search — finding implementations without knowing exact names, exploring unfamiliar codebases, or locating code by concept.
- ▌ Use Command Template · jamie-bitflightUse when creating new Claude Code skills following established patterns and templates. Activates on "create a new skill", "add a skill to plugin", or "write skill from template" requests. Note — commands are deprecated; this skill creates SKILL.md files instead. Produces correctly structured skill files with valid frontmatter and body.
- ▌ Conventional Commits · jamie-bitflightWhen writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.
- ▌ Setup Skill Discovery · jamie-bitflight bundleUse when creating or updating the project skill discovery config — generates or regenerates .dh/skill_discovery.yaml by scanning the repo to infer tech stack, inventorying installed skills via npx skills list, loading candidate skill content before suggesting, and writing a config-driven skill injection file. Triggers on /dh:setup-skill-discovery invocations and programmatic --auto calls from add-new-feature Phase 3.
- ▌ Ecosystem Research · jamie-bitflightResearch community usage patterns, real-world gotchas, and client compatibility for a specific known library, tool, or protocol feature. Use when a technical-researcher orchestrator needs community-sourced evidence about a named library or feature — bug reports, workarounds, compatibility gaps, and patterns from issue trackers and discussions. Distinct from the broad ecosystem-researcher agent — this skill targets a KNOWN entity and mines what real users have actually experienced, not what exists in a domain.
- ▌ Final Verification · jamie-bitflightCertifies that a feature achieves its original objectives via goal-backward verification (SAM Stage 7). Use when all tasks pass forensic review — starts from expected outcomes, works backwards to verify each was achieved, and returns CERTIFIED or NOT_CERTIFIED with specific gaps.
- ▌ Impact Measurement · jamie-bitflightQuantitative cost measurement for technical research — token injection costs, payload sizes, context window consumption, and file-level counts from actual repo files. Use when a technical-researcher orchestrator needs the cost dimension of adding or changing something: how many tokens will it inject, how big are the artifacts, what is the context window impact? This is NOT blast-radius analysis (which files break) — it covers size, tokens, and performance cost only.
- ▌ Task Decomposition · jamie-bitflightDecomposes a contextualized plan into atomic, independently executable tasks with complete embedded context, registered through the plan API. Use after SAM Stage 3 Context Integration produces the contextualized plan artifact — when the plan is ready for task generation with CLEAR ordering, CoVe checks, and dependency graphs for parallel execution.
- ▌ Create Feature Task · jamie-bitflightUse when creating a new feature development task — scaffolds a structured task file at .claude/tasks/{feature-name}.md with phased breakdown (Design, Implementation, Testing, Documentation), acceptance criteria, context preservation, and TaskCreate tracking. Activates on "create a feature task", "set up development tracking", "plan a feature implementation", or when preparing work for python-cli-architect or python-pytest-architect agents.
- ▌ Pypi Readme Creator · jamie-bitflight bundleGenerates professional PyPI-compliant README files in Markdown or reStructuredText. Use when creating a Python package README for PyPI publication, converting between README.md and README.rst formats, validating markup with twine check before publishing, configuring the readme field in pyproject.toml, integrating sphinx-readme to generate PyPI-compatible RST from Sphinx docs, troubleshooting rendering errors on PyPI, or previewing README rendering locally with grip or docutils.
- ▌ Python3 Add Feature · jamie-bitflightExecutes a four-phase feature addition workflow (Discovery, Planning, TDD Implementation, Verification) for Python projects. Use when adding a new feature end-to-end — discovering project structure and integration points, drafting a feature spec with MoSCoW-prioritized requirements and BDD acceptance criteria, implementing via test-first TDD cycles, then verifying with ruff lint, ty type checks, and 100% coverage on new code.
- ▌ Python3 Stdlib Only · jamie-bitflight bundleUse when building dependency-free Python 3.11+ scripts for airgapped, stdlib-only, or restricted environments where third-party package installation is prohibited — triggers on "stdlib-only", "airgapped", "no dependencies", "no internet", "restricted environment", or confirmed environments where external packages cannot be installed.
- ▌ Python3 Test Design · jamie-bitflightGuides pytest test suite architecture and coverage strategy for Python 3.11+ projects. Activates when designing test architecture, planning test pyramid distribution, choosing between unit/integration/property-based/BDD strategies, structuring fixture hierarchies, configuring branch coverage thresholds, or applying mutation testing to critical code paths.
- ▌ Brainstorming Skill · jamie-bitflight bundleYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.
- ▌ Context Integration · jamie-bitflightUse when the PLAN artifact from SAM Stage 2 needs contextualization against actual codebase state — grounds the design plan in reality by performing scope analysis (NEW/MODIFY/COMPLETE classification), conflict detection between plan assumptions and codebase patterns, and resource mapping to concrete file paths and integration points. Produces an updated ARTIFACT:PLAN registered via MCP with a Contextualization section appended.
- ▌ Development Harness · jamie-bitflight bundleRoutes to the correct dh skill entry point by intent. Use when unsure which development-harness skill to invoke, starting a development workflow, or invoking /dh directly. Covers capture, groom, plan, execute, single task, quality gates, and milestone routing.
- ▌ Validation Protocol · jamie-bitflightScientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, refactoring, or implementation is complete — enforces reproduce-broken-state then define-success-criteria then apply-fix then verify-outcome. Success means observing intended behavior, not absence of errors.
- ▌ Perl Environment Setup · jamie-bitflightThis skill should be used when the user asks to "install perlbrew", "set up Perl environment", "install Perl version", "manage Perl versions", "switch Perl version", "install plenv", or mentions Perl version management, development environment setup, or multiple Perl installations.