hermes-agent-skills

Use when the user needs DevOps or SRE help including CI/CD pipelines, Docker optimization, Kubernetes manifests, infrastructure safety, or production log analysis.

Use when the user needs expert Python engineering help including code review, performance profiling, pytest generation, package scaffolding, or static type guidance.

Use when the user presents a vague, ambiguous, or underspecified task. Conducts structured multi-turn dialogue to extract true requirements with ~95% clarity before any code is written.

Use when the user needs DevOps or SRE help including CI/CD pipelines, Docker optimization, Kubernetes manifests, infrastructure safety, or production log analysis.

Use when the user needs expert Python engineering help including code review, performance profiling, pytest generation, package scaffolding, or static type guidance.

Use when debugging complex issues involving multiple modalities (frontend + backend, API + UI, terminal + browser). Coordinates Hermes Agent's built-in debugger, browser, terminal, and vision tools for systematic root-cause analysis.

Use when implementing logic, fixing bugs, or changing behavior. Enforces strict RED-GREEN-REFACTOR cycle with the test pyramid (80/15/5) and Beyonce Rule — tests before code, always.

Use when starting a new feature, project, or significant refactor. Writes a comprehensive PRD/spec document before any implementation code, following the "spec-first, code-second" principle.

Use before starting any code generation task. Reads Hermes Agent's SOUL.md to dynamically adapt code style, comment tone, documentation voice, and architectural decisions to match the agent's defined persona.

Use after completing a complex task, fixing a tricky error, or discovering a reusable workflow. Analyzes the execution record, proposes skill improvements, and feeds into Hermes Agent's self-learning loop — the meta-skill that makes all other skills better.

Use when setting up or optimizing CI/CD pipelines. Generates GitHub Actions workflow configurations following best practices — matrix builds, caching, artifact management, and deployment gates.

Use before merging or committing code. Performs six-axis code quality gating — security, complexity, style, test coverage, documentation, and dependency health. Blocks low-quality code from entering the main branch.