harness-engineering

A comprehensive guide to creating custom slash commands for Claude Code.

This directory contains slash commands organized by category for easy discovery and management.

Conduct comprehensive codebase research using parallel sub-agents

Execute implementation plans from research-plans/plans/ directory

Executes a plan with gated checks, atomic commits, build/package/deploy, full validation, and immutable execution logs

This directory contains specialized AI agents organized by category.

Use this agent when you need to analyze recently implemented code changes to identify issues, inconsistencies, or areas needing fixes. This agent coordinates research sub-agents to examine file locations and implementation logic, then synthesizes findings into an actionable report focusing only on problems that require attention. <example>Context: The user has just implemented a new feature or made significant code changes and wants to verify the implementation quality. user: "I've just finished implementing the new authentication flow, can you check if there are any issues?" assistant: "I'll use the code-synthesis-analyzer agent to examine your recent implementation and identify any issues that need fixing." <commentary>Since the user has completed an implementation and wants to check for issues, use the code-synthesis-analyzer agent to research the changes and synthesize findings.</commentary></example> <example>Context: After a refactoring session, the user wants to ensure no logic was broken. user: "I refactored the payment processing module, please verify if anything needs fixing" assistant: "Let me launch the code-synthesis-analyzer agent to research your refactoring and report any issues found." <commentary>The user has made changes and specifically wants to know about potential issues, making this a perfect use case for the code-synthesis-analyzer agent.</commentary></example>

Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)

Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.

Use this agent when you need to analyze a bug, gather comprehensive context about it, and create a GitHub issue for tracking. The agent will investigate the bug's symptoms, potential causes, affected code areas, and reproduction steps, then use the GitHub CLI to create a well-documented issue. If unable to create the issue automatically, it will provide the user with complete instructions for manual creation. <example>Context: User encounters a bug in their application and wants to create a GitHub issue with proper documentation. user: "I'm getting a TypeError when calling the calculateTotal function with null values" assistant: "I'll use the bug-issue-creator agent to analyze this bug and create a GitHub issue for it" <commentary>Since the user reported a bug and needs it documented as an issue, use the bug-issue-creator agent to gather context and create the GitHub issue.</commentary></example> <example>Context: User discovers unexpected behavior in production and needs to document it. user: "The API is returning 500 errors when processing orders over $10,000" assistant: "Let me use the bug-issue-creator agent to investigate this issue and create a GitHub issue with all the relevant details" <commentary>The user found a production bug that needs investigation and documentation, so the bug-issue-creator agent should be used.</commentary></example>

This skill should be used when creating, refreshing, or validating a repository `AGENTS.md` so it stays concise, current, and grounded in repository evidence. Use when `AGENTS.md` is missing or stale, after refactors or tooling changes, when new docs become the system of record, or when adding lightweight drift checks.

Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs. Creates sgconfig.yml, rule files, and rule tests. Use when adding structural linting, banning legacy patterns, or implementing ratchet gates.

Run or continue a differential debugging session between two implementations, traces, captures, or outputs. Record artifact identity, exact commands, first mismatch progression, findings, validation, and next probe in a durable session log.

Execute implementation plans from .artifacts/plan/. Focus on EXECUTING ONLY - no planning, no fixes outside plan scope. Uses gated checks, atomic commits, and maintains a single execution log in .artifacts/execute/. Use when the user says "execute this plan" or provides a plan path.

Map a repository's mechanical harness layers: canonical check command, local and CI gates, architecture boundaries, structural rules, behavioral verification, docs ratchets, evidence workflows, and operator-facing surfaces. Use when you need to understand how a repo keeps change safe.