Use when source code must be implemented, debugged, refactored, or code-audited through a plan, execution, test, and report loop. Not for requirements-only changes, new empirical experiments, or document-only editing.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add dmlguq456/hearting --skill autopilot-code --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Autopilot Code?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dmlguq456-autopilot-code-hearting)More formats (shields.io, HTML) on the badges page.
---
# GENERATED METADATA — edit harness-manifest.json, then run tools/generate.py.
name: autopilot-code
description: "Use when source code must be implemented, debugged, refactored, or code-audited through a plan, execution, test, and report loop. Not for requirements-only changes, new empirical experiments, or document-only editing."
argument-hint: "--mode dev|debug <task/plan/error description> [--from <step>] [--intensity direct|quick|standard|strong|thorough|adversarial] [--user-refine]"
metadata:
group: entry
fam: code
invocation_class: entry-router
modes: ["dev", "debug", "audit"]
blurb: "Code-work entrypoint that detects spec context and closes the plan→execute→test→report loop."
use_when: "Use when source code must be implemented, debugged, refactored, or code-audited through a plan, execution, test, and report loop."
not_for: "Not for requirements-only changes, new empirical experiments, or document-only editing."
---
# autopilot-code
This is a compact pre-approval entry router. Its manifest-owned frontmatter is
the authoritative discovery metadata; it intentionally contains no execution
procedure.
## Pre-approval boundary
Use only this router, `harness-manifest.json`, and `core/WORKFLOW.md §0.2` to
propose a route. Present the one-time confirmation in `core/WORKFLOW.md §0.4`
unless the same route and scope are already approved. Do not load references
before approval.
## Post-approval owner contract
After approval, direct/quick sessions and the `standard+` dispatch-depth-1 owner load
`capabilities/autopilot-code.md`, then use the Reference Index below. Assigned
stage workers load only their assigned stage contracts.
## Reference Index
| File | Load when | Obligation |
|---|---|---|
| [`references/owner-execution.md`](references/owner-execution.md) | After approval, by the selected direct/quick session or dispatch-depth-1 owner | Read the complete execution procedure before material work. This is the router's only post-approval reference edge. |
## Guard pointer
Follow the portable artifact, worktree, role, and verification guards in the
selected owner contract. Before the first durable capability artifact, compile
and bind the checked route even for direct intensity; direct is a compiled
inline node, not route absence. A restriction on native subagents/agents is
surface-local and never selects direct execution. Runtime projections must
report unsupported mechanics and must not claim physical instruction masking,
token, billing, or cost savings without verified evidence.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!