bundles

Summarize git history, staged diffs, or PR changes into clear, human-readable summaries grouped by theme.

Generate Conventional Commits-compliant commit messages from staged changes or a description of work done.

Build marketing-grade code displays for the Musher marketing site -- split-panel code-then-output layouts, CSS-only syntax highlighting, tabbed views, and terminal chrome. Use when implementing IA Section 3 (Mechanism), building code blocks, creating terminal demos, highlighting YAML/CLI output, or adding copy buttons to code. Triggered by: code display, code block, syntax highlighting, code-then-output, split panel code, terminal chrome, YAML highlight, CLI output, code snippet, tabbed code, multi-language code, mechanism section code, bundle yaml, pipeline yaml, marketing code.

Scaffold marketing page sections from IA definitions into Svelte 5 components. Use when building section components from the Information Architecture, translating archetypes to markup, mapping content slots to elements, or creating section scaffolds. Triggered by: scaffold section, build section, IA to component, section component, hero section, mechanism section, value grid, proof block, community block, CTA block, social proof bar, content slot, archetype component, layout pattern, section scaffold, marketing component.

Analyze CSV data by computing aggregations, filtering rows, and generating readable summaries. Use when working with tabular data files in a container environment where the agent creates and manipulates files directly.

Ensure local development environments match CI/CD environments for consistent behavior including shared version sources, devcontainer reuse in CI, reproducible dependency installation, environment variable parity, Docker image sharing, and lock file enforcement. Use when diagnosing works-on-my-machine issues, designing CI pipelines that mirror local dev, or auditing environment parity. Triggered by: CI alignment, CI environment, works on my machine, CI parity, environment parity, CI local match, GitHub Actions, CI pipeline, CI docker, reproducible builds, lock file, frozen lockfile.

Audit a repository for developer environment configuration completeness covering version pinning, editor config, task runner, env var documentation, setup scripts, devcontainer presence, Docker configuration, and CI alignment. Produces a gap analysis with maturity scoring and prioritized recommendations. Use when assessing a project's developer experience maturity, onboarding to a new codebase, or evaluating developer environment quality. Triggered by: environment audit, dev experience audit, DX audit, environment completeness, environment review, onboarding review, dev setup review, environment maturity, environment assessment, developer experience.

Design and configure task runner configurations including Taskfile.yml (Task), Makefile (Make), justfile (just), npm/pnpm scripts, and deno tasks. Covers task naming conventions, dependency ordering, cross-platform compatibility, variable passing, help/documentation generation, and common task patterns for development workflows. Use when creating or reviewing project task definitions, choosing between task runners, or standardizing development commands across a team. Triggered by: taskfile, Taskfile.yml, makefile, Makefile, justfile, npm scripts, task runner, make target, dev commands, build automation, pnpm scripts, deno task.

Design Docker and Docker Compose configurations for local development environments including multi-service stacks, hot-reload volume mounts, database and cache services, networking, health checks, development-specific overrides, Dockerfile multi-stage patterns, and .dockerignore optimization. Use when creating or reviewing docker-compose.yml for local dev workflows, designing multi-stage Dockerfiles, or troubleshooting container networking. Triggered by: docker compose, docker-compose, Dockerfile, docker development, multi-stage, docker volume, docker network, container development, compose yaml, dockerignore, docker health check, docker dev.

Design and configure VS Code Dev Container environments including devcontainer.json schema, feature selection and pinning, lifecycle hooks (postCreateCommand, postStartCommand, postAttachCommand), Docker and Docker Compose integration, multi-container setups, port forwarding, mount configuration, and GPU passthrough. Use when creating or reviewing .devcontainer/ configurations, selecting features, troubleshooting container startup, or designing team-shared development containers. Triggered by: devcontainer, dev container, devcontainer.json, container development, codespace, development container, remote container, container feature, postCreateCommand, postStartCommand.

Configure shared editor and IDE settings including .editorconfig for cross-editor formatting basics, VS Code workspace settings (.vscode/settings.json, extensions.json, launch.json), JetBrains shared configurations, and conflict resolution between editor configs and formatters. Use when standardizing editor behavior across a team, reviewing IDE configuration files, or resolving conflicts between .editorconfig and Prettier/ESLint. Triggered by: editorconfig, vscode settings, extensions.json, launch.json, editor configuration, IDE settings, workspace settings, format on save, recommended extensions, debug configuration, code workspace.

Design environment variable management patterns including .env.example templates, direnv (.envrc) configuration, secret vs non-secret classification, startup validation, naming conventions, and Docker Compose env_file integration. Use when establishing env var conventions, reviewing secret handling, configuring direnv layouts, or documenting environment requirements. Triggered by: env, .env, environment variables, env.example, envrc, direnv, dotenv, secrets, environment configuration, env template, env vars.

Configure and enforce toolchain version pinning using .tool-versions (asdf/mise), .nvmrc, .python-version, .ruby-version, .node-version, and runtime-specific version files. Covers version manager selection, pinning granularity, conflict resolution across multiple version files, CI alignment, and monorepo versioning strategies. Use when standardizing runtime versions across a team, resolving version conflicts, or auditing version file consistency. Triggered by: tool-versions, asdf, mise, nvm, nvmrc, node-version, python-version, ruby-version, version pinning, runtime version, fnm, pyenv, rbenv, version manager.

Orchestrate end-to-end developer environment scaffolding for a repository by first auditing existing configuration, then delegating to specialized skills for devcontainers, task runners, version management, editor config, env vars, Docker, and setup scripts. Use when bootstrapping a complete developer environment from scratch, upgrading an existing setup, or running a full environment audit followed by remediation. Triggered by: scaffold environment, bootstrap environment, setup dev environment, create dev environment, environment setup, dev env, full environment, workspace bootstrap, project environment.

Design workspace initialization scripts and onboarding automation including setup.sh/setup scripts, dependency bootstrapping, prerequisite verification, health checks, cross-platform considerations (macOS/Linux/WSL), and first-run developer experience. Use when creating setup scripts, reviewing onboarding flows, or designing developer-friendly bootstrap experiences. Triggered by: setup script, workspace setup, onboarding, bootstrap, dev setup, first run, getting started, developer onboarding, setup.sh, project setup, workspace initialization.

Score a repository's documentation health across five dimensions (Presence, Completeness, Currency, Discoverability, Quality) and produce a severity-prioritized remediation report. Covers README, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT, CHANGELOG, LICENSE, issue templates, PR template, CODEOWNERS, GOVERNANCE, and FUNDING.yml. Use when auditing repo health, assessing documentation gaps, or prioritizing documentation improvements. Triggered by: repo audit, documentation health, community health check, repo health score, documentation gaps, missing docs.

Scaffold a new repository's community health files with starter templates for README, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT, CHANGELOG, issue templates, PR template, CODEOWNERS, GOVERNANCE, and FUNDING.yml. Use when initializing a new repo, bootstrapping community health files, or setting up GitHub discoverability. Triggered by: scaffold repo docs, community health files, initialize repo, repo setup, bootstrap repo, new repo documentation.

Author community governance documents including CODE_OF_CONDUCT.md based on Contributor Covenant 2.1, SUPPORT.md with support channel routing, GOVERNANCE.md with decision-making models and maintainer paths, and FUNDING.yml for sponsorship configuration. Use when establishing community standards, defining support channels, or documenting project governance. Triggered by: code of conduct, community standards, support channels, governance model, funding, sponsor button, maintainer path, contributor covenant.

Author CONTRIBUTING.md files that lower the barrier to first contribution with development setup instructions, workflow guidance, coding standards, testing requirements, and PR process documentation. Adapts to project toolchain and language ecosystem. Use when writing contributor guidelines, improving onboarding, or defining PR workflows. Triggered by: CONTRIBUTING, contributing guide, contributor guidelines, development setup, PR process, how to contribute.

Author GitHub configuration files including YAML-based issue templates (bug report, feature request), pull request templates, CODEOWNERS for automatic reviewer assignment, and CHANGELOG following Keep a Changelog 1.1.0 format. Use when setting up issue forms, defining PR checklists, configuring code ownership, or establishing changelog conventions. Triggered by: issue template, PR template, pull request template, CODEOWNERS, code owners, CHANGELOG, keep a changelog, issue form, bug report template, feature request template.

Author compelling README.md files with structured sections for project overview, quick start, installation, usage examples, and contribution links. Adapts structure by project type (library, application, framework, CLI tool). Use when writing or improving a project README, creating first impressions, or optimizing repo discoverability. Triggered by: README, readme, project overview, repo description, quick start, getting started, project introduction.

Author SECURITY.md files that enable responsible disclosure with supported versions tables, reporting channels, response timelines, severity classification, and safe harbor provisions. Use when writing security policies, setting up vulnerability reporting, or defining disclosure processes. Triggered by: SECURITY, security policy, vulnerability reporting, responsible disclosure, security contact, supported versions.

Generate clear architecture explanations for codebases and systems. Use when a developer needs to understand how components interact, where data flows, or how a system is structured at a high level.

Explore repository structure, dependencies, and conventions to build deep understanding of a codebase. Use when onboarding to a new project, investigating unfamiliar code, or mapping dependencies before making changes.

Analyze test coverage gaps and suggest targeted tests for uncovered code paths. Use when evaluating test adequacy, identifying missing edge case tests, or improving confidence before a release.

Generate release notes from git history, pull request descriptions, and changelog entries. Use when preparing a release, summarizing changes for stakeholders, or updating a CHANGELOG file.

Explore repository structure, map dependencies, and surface conventions before making changes. Use when onboarding to a new repo, investigating unfamiliar code, or preparing context for a review.

Perform systematic pull request reviews covering correctness, security, performance, and maintainability. Use when reviewing PRs, providing code feedback, or conducting pre-merge checks.

Guide structured audit execution for contract enforcement compliance using a 5-category question bank covering Contract Structure, Breaking Change Detection, Conformance Testing, SDK Generation, and Enforcement Pipeline, with Pass/Warn/Fail severity model mapped to Critical/Major/Minor/Cosmetic levels, compliance scorecard, enforcement maturity assessment, and improvement roadmap. Use when conducting contract enforcement audits, reviewing enforcement posture, auditing pipeline completeness, assessing enforcement maturity, or prioritizing enforcement technical debt. Triggered by: contract audit, enforcement audit, pipeline audit, contract compliance, enforcement maturity, enforcement posture, contract quality gate, enforcement scorecard, enforcement review.

Guide design, review, audit, and implementation of breaking change detection for API contracts using oasdiff integration, breaking change classification with ERR and WARN severity levels, backward compatibility rules for request and response schemas, deprecation window enforcement with sunset headers, and CI gate configuration for merge blocking. Use when configuring breaking change detection, auditing backward compatibility, reviewing deprecation policies, or setting up oasdiff CI gates. Triggered by: breaking change, oasdiff, backward compatibility, deprecation, sunset header, API versioning, schema evolution, breaking diff, contract diff, API diff, compatibility check, semver.

Guide design, review, audit, and implementation of monorepo contract structure including workspace configuration for Turborepo and Nx, packages/contract/ directory layout, artifact classification (editable spec, generated outputs, implementation source), cross-package dependency rules, and build orchestration for contract-dependent packages. Use when designing monorepo contract layout, auditing artifact separation, reviewing workspace config, or structuring contract packages. Triggered by: monorepo contract, packages/contract, artifact separation, workspace config, Turborepo, Nx, contract layout, editable spec, generated artifacts, contract directory, contract package, repo structure.

Guide design, review, audit, and implementation of contract enforcement CI pipelines covering the 5-stage pipeline (lint, bundle, diff, backend validate, frontend conform), gate configuration with blocking and warning modes, stage dependency ordering, parallel vs sequential execution, artifact passing between stages, and pipeline observability. Use when designing contract enforcement CI, auditing pipeline completeness, reviewing gate modes, or configuring enforcement stages. Triggered by: enforcement pipeline, CI pipeline, contract CI, lint stage, bundle stage, diff stage, validate stage, conform stage, gate config, blocking mode, warning mode, pipeline stages, CI gates, contract enforcement.

Guide design, review, audit, and implementation of SDK generation governance including @hey-api/openapi-ts configuration, prohibiting manual fetch wrappers, tsc --noEmit conformance checks, generated SDK consumption rules, regeneration triggers, and SDK package publishing strategy. Use when configuring SDK generation, auditing manual API wrappers, reviewing generated client usage, or setting up SDK regeneration pipelines. Triggered by: SDK generation, openapi-ts, hey-api, generated client, fetch wrapper, API client, type generation, SDK config, client generation, codegen, generated types, SDK governance.

Guide design, review, audit, and implementation of contract conformance testing using Schemathesis integration with from_asgi() for FastAPI applications, stateful testing with OpenAPI link-based state machines, test database management for conformance test suites, response schema validation, and coverage measurement against the OpenAPI specification. Use when configuring Schemathesis, auditing contract test coverage, reviewing stateful test strategies, or setting up conformance test infrastructure. Triggered by: contract testing, Schemathesis, conformance testing, schema validation, stateful testing, OpenAPI links, from_asgi, property-based testing, API testing, contract test, spec conformance, response validation.

Guide structured audit execution for OpenAPI specification compliance using a 9-category question bank covering Spec Metadata, Operation Identifiers, Tag Hierarchy, Component Reuse, Advanced Operations, Extension Governance, Spec Structure, Authoring Model, and Change Workflow, with Pass/Warn/Fail severity model mapped to Critical/Major/Minor/Cosmetic levels, compliance scorecard, Spectral/Redocly/Vacuum ruleset recommendations, and CI pipeline integration patterns. Use when conducting OpenAPI spec audits, reviewing specification compliance, auditing spec quality, prioritizing spec technical debt, or setting up CI spec governance. Triggered by: spec audit, OpenAPI audit, specification audit, spec compliance, spec quality, spec linting, Spectral rules, Redocly, Vacuum, spec governance, spec scorecard, spec quality gate, specification review.

Guide evaluation, selection, and governance of API specification authoring models including design-first, code-first, and hybrid approaches, unidirectional authority flow from spec to implementation, dual-schema maintenance tax assessment, source-of-truth governance policy formalization, and criteria for choosing the right model for a given team and API. Use when evaluating authoring models, formalizing source-of-truth policy, auditing authority flow, or assessing dual-schema maintenance tax. Triggered by: authoring model, design-first, code-first, hybrid, source of truth, authority flow, spec-first, contract-first, dual schema, maintenance tax, governance model, API workflow, spec authority.

Guide design, review, audit, and implementation of API specification change workflows including the Golden Path sequence (design, generate, implement, verify, deploy), cross-team coordination patterns for spec changes, spec-change PR conventions and review requirements, backward-compatible change techniques, and versioning strategies for spec evolution. Use when designing spec change workflows, auditing change processes, reviewing PR conventions, or implementing backward-compatible changes. Triggered by: change workflow, Golden Path, spec change, PR convention, backward compatible, spec evolution, change process, cross-team coordination, spec PR, API change, change management, spec versioning, workflow governance.

Guide design, review, audit, and implementation of OpenAPI component reuse patterns including $ref usage, inline schema anti-patterns, component organization strategies, schema composition with allOf oneOf and discriminator, RFC 9457 ProblemDetails as reusable component, and SDK generation impact of composition choices. Use when reviewing $ref patterns, auditing inline schemas, organizing components, designing schema composition, or implementing discriminated unions. Triggered by: $ref, component reuse, inline schema, allOf, oneOf, discriminator, schema composition, ProblemDetails, RFC 9457, components section, schema organization, DRY schemas, ref pattern, reusable schema.

Guide design, review, audit, and implementation of multi-file OpenAPI specification structure including directory layout conventions for paths, components/schemas, components/parameters, and components/responses, file-level $ref strategies, bundling with Redocly CLI into single openapi.json, split vs monolithic anti-patterns, and root file conventions. Use when designing multi-file spec layouts, auditing spec directory structure, reviewing $ref file strategies, or configuring spec bundling. Triggered by: multi-file spec, spec structure, spec layout, $ref files, Redocly bundle, split spec, spec directory, paths directory, schemas directory, spec organization, file structure, spec files.

Triggers on: create a bundle, name a bundle, add a new bundle, scaffold a bundle folder