auto-master-skills

Use when the user asks for /auto-copy, auto copy, autocopy, $auto-copy, or legacy /auto-fork, or points at a GitHub project or external codebase and wants its features or whole product copied, ported, forked, adapted, or rebuilt natively into one of their projects — including cross-stack ports such as a Python project rebuilt in Rust. Reviews the source first, plans a behavior-by-behavior extraction, and implements with per-feature QA only after explicit approval.

Use when the user asks for /auto-doc, /autodoc, $auto-doc, complete project docs, project technical docs, public/private docs, source-grounded docs, docs extraction, docs for training an assistant, docs audit, source map, deep dives, evidence-backed documentation, or converting private technical truth into public-facing behavior docs for any project. Always builds a complete project corpus with private technical docs, public behavior docs, safety audits, coverage audits, and assistant ingest JSONL; incomplete or single-batch runs are invalid.

Manage large, multi-phase builds end to end through research, planning, implementation, review, security review, and QA. Use when the user asks for /manage, auto-manage, autonomous project management, roadmap execution, or a complete build that needs bounded slices and risk-tiered verification. Work inline by default and use workers or independent reviewers only when their separation materially improves speed or confidence.

Execute an approved roadmap autonomously in small verified slices until complete or genuinely blocked. Use when the user asks for auto-pilot, autonomous roadmap execution, continued implementation, or bounded development with risk-tiered tests, execution receipts, regression checks, and loop protection.

Create a structured, verification-ready implementation plan without executing it. Use when the user asks for /autoplan, auto-plan, a development roadmap, or a plan with bounded slices, mechanical acceptance criteria, security boundaries, rollback, risk-tiered QA, and regression controls.

Plan or execute risk-tiered QA with reproducible evidence. Use when the user asks for /autoQA, autoQA, auto-qa, smoke or regression testing, validation before review/merge/deploy/release, or proof that a change works through baseline comparison, execution receipts, and real frontend interaction.

Turn confirmed workflow failures into small durable recurrence guards. Use after a user correction, verified false claim, confirmed implementation mistake, or repeated-failure circuit-breaker event; do not use for speculation, preference changes, expected failing tests, or unrelated environment failures.

Use when the user asks for /auto-research, auto research, autoresearch, a research plan, or a research scope; when a discussed feature needs research before planning; or when auto-manage enters its research phase.

Generate and maintain repo or feature documentation for authorized local projects. Use when the user asks for Master-Docs, master-docs, full repo docs, feature docs, internal technical docs, public or customer-support docs, codebase graph documentation, documentation refresh, or diff-aware documentation updates. Produces private technical docs and sanitized public docs outside the repo using a manifest/diff workflow.

Audit an authorized local repo or feature for wasted memory, CPU, rendering, network, disk, battery, and unnecessary complexity. Use for Master-Optimize, performance review, resource audits, leak hunts, rendering bloat, or lean-code opportunities. Produces an evidence-backed analysis report with measurement receipts and risk-triggered independent review; it never changes project code.

Run a full release-candidate QA gate for authorized local projects. Use for Master-QA, release QA, installer or desktop/web validation, regression sweeps, go/no-go decisions, or the final quality wall before public release. Requires baseline comparison, reproducible execution receipts, real frontend interaction, and an evidence-backed release decision.

Plan and execute safe behavior-preserving refactors for authorized local projects. Use for Master-Refactor, repo or feature cleanup, code simplification, periodic maintenance sweeps, optimization candidates, or refactor planning. Starts with measured analysis and a ranked candidate report, requires approval before code, then uses isolated slices, characterization tests, execution receipts, and regression deltas.

Run a pre-release product trust and readiness review for authorized local projects. Use when the user asks for Master Release Review, master-release-review, release readiness review, product trust review, privacy review, dependency review, configuration review, production build review, source leak review, or final review before public distribution. Produces a findings-backed GO / NO-GO / GO WITH KNOWN RISKS report outside the repo.

Review authorized local repos for public-release readiness and accidental private material before open-source publishing or public sharing. Use when the user asks for Master-Sanitize, master-sanitize, repo sanitization, open-source readiness, public repo review, private-to-public cleanup, confidential material review, denylist scan, sensitive file review, or safe export planning. Defaults to review/report only and writes findings outside the repo.