Agent-Skills

autofix

Apply approved fixes for unresolved CodeRabbit review comments, Codex P1-P3 findings, PR feedback, and code review issues with validation evidence. Use when asked to address review comments, fix review findings, clear unresolved comments, or autofix PR feedback.

he-ideate

Generate and compare grounded product or engineering directions with tradeoffs. Use when users want possibilities, critique, or direction-setting before a spec.

he-improve

Improve existing Harness Engineering implementations or workflows with evidence-backed changes. Use when users ask for targeted enhancement of shipped or drafted work.

he-fix-bugs

Debug and repair validated Harness Engineering defects with bounded scope, reproduction evidence, root-cause notes, regression protection, and validation proof. Use when a bug is already evidenced and the fix should not expand into broad improvement work.

he-reframe

Create evidence-backed HE reframe migration programs. Use when structural drift, routing ambiguity, or source-prompt gaps need phased rollback-safe execution.

he-reliability-review

Review services, APIs, and multi-component systems for reliability risks including failure modes, cascading failures, resilience gaps, and SLO readiness. Use when the work involves new services, significant service changes, multiple external dependencies, or high blast-radius failure scenarios.

he-prune-branches

Review and prune stale branches safely. Use when branch cleanup needs evidence, protected-branch caution, PR awareness, and non-destructive recommendations.

he-strategy

Compress HE cognition artifacts into evidence-backed strategy. Use when intent, review, triage, ADR, core, or source-prompt comparison evidence needs durable direction.

he-deepen-spec

Deepen an existing system or UI spec so boundaries, lifecycle rules, failure handling, and validation are strong enough for planning. Use when the user wants Harness Engineering spec hardening or a requirements review pass before planning.

plugin-router

Analyze broad, mixed, or unclear Plugin Factory follow-up requests and select the correct plugin lane. Use when plugin intent lacks a clear lane owner.

he-work

Implement approved Harness Engineering work. Use when a plan, todo list, or tiny spec needs traceable delivery and validation.

skillify

Converts a successful repeatable workflow into a validated Codex SKILL.md package with triggers, examples, evals, and release checks. Use when users say create a skill, skillify this, package a workflow, save this process, make reusable guidance, or turn a session into a skill.

he-router

Route ambiguous Harness Engineering requests to one lifecycle stage when users ask where to start, resume, plan, implement, review, debug, schedule a heartbeat, or resolve domain terminology.

he-heartbeat

Create bounded Harness Engineering follow-up checkpoints, resume packets, stop conditions, and automation-safe handoff notes. Use when work must continue later without losing state or silently becoming autonomous execution.

plugin-builder

Harden and validate Codex plugin packages with contract-grade checks before install or release. Use when the deliverable is a plugin package that needs conversion or hardening.

bash-hygiene

Review, create, and validate Bash scripts when shell work needs strict mode, quoting safety, portability, or interpreter-compatible behavior.

skill-builder

Analyze and harden Codex skills and plugin packages for contract quality, eval coverage, and safety compliance. Use this skill when an existing package is approaching release and needs evidence-backed validation.

codex-agent-creator

Create, validate, install, fold, or troubleshoot Codex custom subagent roles, role TOML config files, agent configuration, custom roles, subagent setup, and discoverability wiring. Use when a user asks for a Codex agent role, reviewer agent, role config, TOML role file, or overlapping agents to merge.

he-code-review

Review PRs, branches, diffs, and workflow artifacts for package-level go/no-go readiness with severity-ranked synthesis. Use when users need readiness synthesis rather than detailed technical-risk critique.

he-work

Executes bounded implementation work from approved specs, plans, issues, or small fixes by editing files, running validation, preserving unrelated work, and recording rollback and handoff evidence. Use when asked to implement, execute a plan, apply changes, or build a scoped feature.

he-technical-review

Review diffs, PRs, specs, plans, or review-feedback items and return severity-ranked engineering findings with exact locations. Use when technical risks or feedback correctness must be verified before implementation.

skill-refactor

Scan Codex session history for skill failures, usage patterns, and coverage gaps. Use when the user wants daily skill-health monitoring or evidence-backed recommendations about installing, improving, merging, or pruning skills.

skillify

Capture a completed Codex workflow as a reusable SKILL.md package by analyzing session context plus optional session-collector evidence, interviewing the user with structured prompts, and writing a validated skill artifact. Use when the user asks to skillify or operationalize a repeatable process.

he-reinforce

Create or refresh evidence-bound Harness Engineering learning artifacts from verified solved problems. Use when a fix worked, a repeated failure should become durable knowledge, or .harness/solutions and Project Brain need maintenance.

he-spec

Create bounded, evidence-backed Harness Engineering specs from approved intent. Use when a selected issue, milestone, reframe phase, or execution slice needs acceptance criteria, traceability, risk gates, and validation boundaries before planning or implementation.