Skill rating

Analyze and improve processes or systems using an explicit semantic model, adaptive instruction resolution, evidence-driven change, and claim-level validation. Use when reviewing process quality, reso

Use when building terminal UI apps with the Textual framework — creating widgets, screens, layouts, handling events, managing reactive attributes, testing with Pilot, snapshot testing with pytest-text

Analyze, improve, or represent processes across a file or directory by delegating to process-siren. Uses the same semantic model and validation loop as single-process work; Mermaid is produced when it

Use when working with ty — this skill's ty policy and required overrides to Astral's official guidance. Pair with `astral:ty` (if installed) for general usage.

When setting up local LLM inference without cloud APIs. When running GGUF models locally. When needing OpenAI-compatible API from a local model. When building offline/air-gapped AI tools. When trouble

Use when starting, stopping, or checking the dot-dash live session dashboard — a real-time browser UI that monitors all active Claude Code sessions, streams transcripts, and supports prompt injection

Orchestrate research entry lifecycle in ./research/ — create, batch-import, refresh stale entries, and validate structure. Use when asked to add a tool, research a URL, document a library, refresh res

Generates and commits conventional-commits messages by analyzing staged git diffs — fast and fork-context safe. Use when the user asks to commit staged changes, needs a type-scope-description message

Compare explicit design/specification contracts with the implementation in a defined change scope. Use to verify signatures, types, schemas, invariants, and other stated contracts without expanding in

Provides agent selection criteria, workflow patterns (TDD, feature addition, code review, refactoring, debugging), quality gates, and python-cli-architect vs stdlib-scripting routing for Python engine

Validate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, im

Synchronize existing documentation with an observed code/configuration/API change while preserving each document's purpose and authority. Use after implementation changes can make documentation stale,

Verify after implementation that a feature achieved its required user/system outcomes. Use for goal-backward post-implementation verification that tests observable behavior rather than merely checking

Claude Code runtime skills router. Use when configuring SKILL.md frontmatter, discovery, invocation, hooks, context forks, substitutions, loading behavior, or headless skill dispatch.

Analyze the causal system-wide impact of a proposed change across behavior, interfaces, state/data, runtime dependencies, tests, documentation, controls, people/processes, and model/prompt/context beh

Verify one falsifiable factual claim against evidence appropriate to the claim. Use when a concrete assertion about software, documentation, configuration, releases, or repository behavior must be cla

Verify that changed components are actually connected into the intended end-to-end system flow. Use when checking imports/exports, registrations, data/control flow, configuration consumption, call pat

Same reverse-thinking method as dh:rt-ica (see dh:rt-ica or dh-glossary for the definition), but localizes any MISSING input to the affected task only, as a non-blocking information-completeness pre-p

Synthesis step in the multi-angle technical research pipeline. Receives structured outputs from all four research angles (api-state, ecosystem-research, impact-measurement, codebase-auditor), applies

Use when independently assessing how bounded Python code could accomplish the same behavior with less maintained code, more Pythonic design, newer language/stdlib capabilities, or well-maintained ecos

Hook JSON input/output API reference — what data hooks receive via stdin and what JSON they can return to control Claude Code behavior. Use when writing hook scripts, checking exit code behavior, buil

Use when building CLI applications with Typer — creating commands, defining arguments and options with enum restrictions, path validation, date and UUID types, composing subcommands, testing with CliR

Use when working with ruff — this skill's ruff policy and required overrides to Astral's official guidance. Pair with `astral:ruff` (if installed) for general usage.

Activates Standard of Excellence enforcement for the current session. Load before starting any task to apply completion standards: finish the whole thing, fix the root cause, ship the complete working

Execute structured acceptance checks and record their observed results for later comparison. Use to capture a pre-change baseline or a post-change verification state without treating expected nonzero

Review changed user-interface or CLI presentation behavior for accessibility failures. Use for an independent accessibility perspective on a defined change set.

Synthesize multiple independent structured review verdicts into one lossless deduplicated punch list. Use when findings from several review perspectives must be merged without inventing, dropping, or

Compatibility routing for callers that previously used the holistic-linting orchestrator workflow. Use only when an existing caller explicitly invokes this skill.

Review a change for material performance regressions or unbounded resource behavior. Use for an independent performance perspective on a defined change set.

Provides 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 de

Review a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective

Review a code change for correctness-maintainability defects not owned by a narrower security/performance/accessibility perspective. Use for an independent quality perspective on a defined change set.

Provides Python-specific code review rules for the dh code-reviewer agent. Activates on pyproject.toml or *.py file detection — enforces uv, ruff, ty, pytest, type annotation, error handling, and Pyth

Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application a

Execute large-scale automated code transformations safely and idempotently. Use when renaming symbols across a codebase, migrating API call-sites, enforcing new patterns at scale, or applying structur

One-line definitions of development-harness (dh) plugin terminology — RT-ICA, ARL, SAM, the S1-S7 pipeline stage names, Impact Radius — each with a pointer to its canonical source file. Use when a dh

Use when independently hunting Python code smells, deviations from engineering standards, maintenance hazards, or suspicious design choices in a bounded review surface.

Works backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current state — classifying each prerequisite as A

Use when installing, updating, or troubleshooting the dasel v3 binary — runs the install script, verifies installation, and diagnoses PATH and download issues

When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing

Activates on any Python task involving *.py files, uv, ruff, ty, pytest, or pyproject.toml — loads the shared Python 3.11+ standards and routes the task to the specialist skill that applies them: TDD,

Use when creating or backfilling AI-categorized daily GitHub releases from branch commits.

Ensemble SOLID review — fans the ruleset across overlapping focused workers over the same code, then reduces by corroboration.

Compatibility router for semantic skill tightening. Delegate goal recovery, authority, semantic conservation, evaluation contracts, and instruction optimization to Skill Lapidary rather than duplicati

Investigate why something happens — confirm the question and success criteria with you, then trace the root cause with an evidence chain.

Compatibility router for skill goal recovery and authority assessment. Delegate to Skill Lapidary's establish-validatable-goals capability rather than maintaining a second goal-contract system in Plug

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mockin

Load 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,

Single-pass SOLID review — dispatches one reviewer over the complete ruleset, emitting the fixed candidate schema.

Compatibility route for existing callers that supply files/scope or quality-gate evidence and need diagnosis and resolution.