All categories
Documentation
Docs, README files, API references, tutorials, specs, and changelogs
- 15,624
- 651
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse documentation skills
Showing 3,937–3,960 of 15,624 skills
- Subagent ContractWhere a dispatched step puts its output, and how it signals state upstream.Votes: 0GitHub stars: 67
- Setup Skill DiscoveryUse 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.Votes: 0GitHub stars: 67
- Review Verdict ContractLoad 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.Votes: 0GitHub stars: 67
- InteropRoutes a Superpowers plan file through the /work-backlog-item pipeline and writes SAM task back-references and chunk annotations into the original plan. Use when given a path to a Superpowers plan file via $ARGUMENTS and needing to create a linked backlog item plus SAM task plan.Votes: 0GitHub stars: 67
- Generate TaskGenerates one worker task prompt conforming to the CLEAR + selective CoVe task design standard and swarm-task-planner structure. Use when creating or rewriting a single task entry or task block inside a plan — providing a title and brief description as input.Votes: 0GitHub stars: 67
- DiscoveryUse when starting a new feature, gathering requirements for an unfamiliar domain, refining a vague idea into actionable scope, or when a user request is ambiguous or underspecified. Conducts SAM Stage 1 discovery — structured requirements gathering through user discussion, asking WHO/WHAT/WHEN/WHY and never HOW. Produces the ARTIFACT:DISCOVERY document containing feature requirements, NFRs, goals, anti-goals, references, and resolved questions. Supports backlog item self-initialization via a ...Votes: 0GitHub stars: 67
- Dh Meta DocsDevelopment harness plugin documentation index. Use when looking up SAM pipeline, backlog lifecycle, SDLC layers, task/plan schema, plan artifacts, quality gates, impact analysis, or dispatch schema documentation.Votes: 0GitHub stars: 67
- Comprehensive Test ReviewReview test effectiveness against authoritative contracts, relevant fault detection, refactor tolerance, boundary fidelity, isolation, and diagnostic value. Use when auditing test quality, reviewing coverage gaps, improving regression protection, or assessing tests after a change.Votes: 0GitHub stars: 67
- Analyze Test FailuresUse 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.Votes: 0GitHub stars: 67
- Data TransformationUse when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INIVotes: 0GitHub stars: 67
- Dasel ReferenceUse when querying, modifying, or converting JSON, YAML, TOML, XML, CSV, HCL, or INI with dasel v3. Complete reference for selectors, functions, conditionals, variables, spread operator, type casting, and format-specific patterns.Votes: 0GitHub stars: 67
- Conventional CommitsWhen 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.Votes: 0GitHub stars: 67
- Bash 52 FeaturesBash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.Votes: 0GitHub stars: 67
- Kaizen ImprovementTransform transcript analysis findings into actionable improvements. Triggers on "generate hooks from findings", "improve agent", "fix anti-pattern", "kaizen improvement", "generate hook proposals", or "create improvement plan". Provides templates for hook generation, agent prompt refinement, skill patches, CLAUDE.md updates, and script automation from analysis data.Votes: 0GitHub stars: 67
- Git History ReconAnalyze git repository history to produce a codebase risk profile before code review. Probes repo size, runs 7 parallel git analysis pipelines (hotspots, bug magnets, bus factor, contributor momentum, firefighting frequency, newly added files), cross-references hotspots with bug magnets to identify high-risk files with primary owner annotation, and writes walkthrough/recon-report.md. Use before code review to prioritize reviewer attention, at the start of linear-walkthrough Phase 1 Discovery ...Votes: 0GitHub stars: 67
- Example Argument SubstitutionTest harness for Claude Code skill argument substitution — demonstrates capture-block pre-declaration, XML tag referencing, unintentional variable corruption in code blocks, and correct placement of shell examples in reference files. Use when verifying substitution behavior before applying a pattern to other skills, testing how arguments flow from skill invocations, or understanding the pre-declaration and reference file pattern with greet/farewell/inspect actions.Votes: 0GitHub stars: 67
- Daily ReleasesUse when creating or backfilling AI-categorized daily GitHub releases from branch commits.Votes: 0GitHub stars: 67
- Create Merge Request ChangelogAnalyze git branches and generate structured MR/PR descriptions with domain-based change categorization — bug fixes, enhancements, technical debt, documentation, testing, build/CI, and non-functional changes. Use when preparing merge request descriptions, pull request bodies, writing changelogs from git diffs, documenting branch changes, or generating release notes. Works with GitHub and GitLab without requiring JIRA or issue tracker integration.Votes: 0GitHub stars: 67
- Handling TransactionsToken transactions and wallet integration for XMTP agents. Use when sending USDC, creating transaction requests, or handling transaction confirmations. Triggers on USDC transfer, wallet calls, or transaction reference.Votes: 0GitHub stars: 54
- Trace Codebase ProvenanceUse when repo origin is unclear, dealing with leaks/sourcemaps/decompiled code, or needing to distinguish source of truth from derived, generated, or reconstructed layersVotes: 0GitHub stars: 2
- Analyze Prompt InfluenceUse when separating prompt-driven behavior from code-driven behavior, understanding what system prompts actually control vs what's hardcoded, or testing how behavior changes under different prompt configurationsVotes: 0GitHub stars: 2
- Documentation Sync EnforcerDetect and prevent docs drift in agent-ready repos. Use when commands, environment variables, routes, migrations, schemas, public APIs, package scripts, architecture, or release behavior changes and docs may need updates.Votes: 0GitHub stars: 3
- Agents Md AuthorGenerate or maintain a minimal high-signal AGENTS.md for coding agents. Use whenever a repo needs agent instructions, an existing AGENTS.md is too long or vague, or project docs/scripts need a concise routing map for Codex.Votes: 0GitHub stars: 3
- Workspace Context Linter 1.0.0诊断始终加载的工作区上下文文件,例如 AGENTS.md、SOUL.md、USER.md、MEMORY.md 和 TOOLS.md。当您想要减少上下文膨胀、检测重复的规则、发现放错位置的内容、识别超重部分或在重新组织核心上下文文件之前审核它们是否仍然符合其预期角色时使用。Votes: 0GitHub stars: 8