Summary
Add a project-scoped user-defined recipe that runs the three core audit skills
(audit-tests, audit-cohesion, audit-arch) in parallel, validates each individually,
and creates a GitHub issue from each validated report. Single-command full audit sweep
that produces three actionable, triaged issues.
Design
Recipe location: .autoskillit/recipes/full-audit.yaml (project-scoped, not bundled)
Step sequence — 3 parallel waves:
Wave 1: Audits (parallel)
audit_tests — run_skill /autoskillit:audit-tests on the target branch
audit_cohesion — run_skill /autoskillit:audit-cohesion on the target branch
audit_arch — run_skill /autoskillit:audit-arch on the target branch
Wave 2: Validations (parallel, after respective audit completes)
validate_audit_tests — run_skill /autoskillit:validate-audit {audit-tests report path}
validate_audit_cohesion — run_skill /autoskillit:validate-audit {audit-cohesion report path}
validate_audit_arch — run_skill /autoskillit:validate-audit {audit-arch report path}
Wave 3: Issue creation (parallel, after respective validation completes)
issue_audit_tests — prepare_issue from the validated audit-tests report
issue_audit_cohesion — prepare_issue from the validated audit-cohesion report
issue_audit_arch — prepare_issue from the validated audit-arch report
Plus terminal done / escalate stop steps.
Ingredients
branch (required) — the branch to audit against
Kitchen Rules
- Each audit and its subsequent validation is independent of the others.
The orchestrator must run all three audit/validate/issue chains in parallel.
- No cross-dependency between audit types — a failure in one chain must not
block or affect the other two.
Output
Three GitHub issues, one per validated audit report:
- Validated audit-tests issue
- Validated audit-cohesion issue
- Validated audit-arch issue
Each issue is created via prepare-issue from the validated markdown report,
which means it arrives pre-triaged with labels and (if applicable) requirements.
Acceptance Criteria
Requirements
RECIPE — Recipe File Structure
- REQ-RECIPE-001: The recipe file must exist at
.autoskillit/recipes/full-audit.yaml and conform to the AutoSkillit recipe schema.
- REQ-RECIPE-002: The recipe must declare
autoskillit_version compatible with the current installed version.
- REQ-RECIPE-003: The recipe must declare a
branch ingredient (required) for the target branch to audit.
PARALLEL — Parallel Execution
- REQ-PARALLEL-001: The three audit steps must be executable in parallel with no ordering dependency between them.
- REQ-PARALLEL-002: Each validate-audit step depends only on its corresponding audit step, not on sibling audits or validations.
- REQ-PARALLEL-003: Each prepare-issue step depends only on its corresponding validate-audit step.
- REQ-PARALLEL-004: A failure in one audit/validate/issue chain must not block or cancel sibling chains.
STEPS — Step Behavior
- REQ-STEPS-001: Each audit step must use
run_skill to invoke its respective audit skill (audit-tests, audit-cohesion, audit-arch).
- REQ-STEPS-002: Each audit step must capture the report output path for downstream consumption.
- REQ-STEPS-003: Each validate-audit step must receive the captured report path from its preceding audit step.
- REQ-STEPS-004: Each prepare-issue step must pass the validated report to
prepare_issue to create a GitHub issue.
ROUTE — Routing and Failure Handling
- REQ-ROUTE-001: Each audit step must route to its corresponding validate-audit step on success.
- REQ-ROUTE-002: Each validate-audit step must route to its corresponding prepare-issue step on success.
- REQ-ROUTE-003: Each prepare-issue step must route to a join/done step on success.
- REQ-ROUTE-004: Any step failure must route to
escalate for that chain.
- REQ-ROUTE-005: The recipe must include terminal
done and escalate stop steps.
VALID — Validation
- REQ-VALID-001: The recipe must pass
validate_recipe without errors.
- REQ-VALID-002: The recipe must be loadable via
load_recipe and executable via kitchen orchestration.
Summary
Add a project-scoped user-defined recipe that runs the three core audit skills
(audit-tests, audit-cohesion, audit-arch) in parallel, validates each individually,
and creates a GitHub issue from each validated report. Single-command full audit sweep
that produces three actionable, triaged issues.
Design
Recipe location:
.autoskillit/recipes/full-audit.yaml(project-scoped, not bundled)Step sequence — 3 parallel waves:
Wave 1: Audits (parallel)
audit_tests—run_skill /autoskillit:audit-testson the target branchaudit_cohesion—run_skill /autoskillit:audit-cohesionon the target branchaudit_arch—run_skill /autoskillit:audit-archon the target branchWave 2: Validations (parallel, after respective audit completes)
validate_audit_tests—run_skill /autoskillit:validate-audit {audit-tests report path}validate_audit_cohesion—run_skill /autoskillit:validate-audit {audit-cohesion report path}validate_audit_arch—run_skill /autoskillit:validate-audit {audit-arch report path}Wave 3: Issue creation (parallel, after respective validation completes)
issue_audit_tests—prepare_issuefrom the validated audit-tests reportissue_audit_cohesion—prepare_issuefrom the validated audit-cohesion reportissue_audit_arch—prepare_issuefrom the validated audit-arch reportPlus terminal
done/escalatestop steps.Ingredients
branch(required) — the branch to audit againstKitchen Rules
The orchestrator must run all three audit/validate/issue chains in parallel.
block or affect the other two.
Output
Three GitHub issues, one per validated audit report:
Each issue is created via
prepare-issuefrom the validated markdown report,which means it arrives pre-triaged with labels and (if applicable) requirements.
Acceptance Criteria
.autoskillit/recipes/full-audit.yamlexists and passesvalidate_recipebranchingredient (required)escalatewithout blocking sibling chainsload_recipe+ kitchen orchestrationRequirements
RECIPE — Recipe File Structure
.autoskillit/recipes/full-audit.yamland conform to the AutoSkillit recipe schema.autoskillit_versioncompatible with the current installed version.branchingredient (required) for the target branch to audit.PARALLEL — Parallel Execution
STEPS — Step Behavior
run_skillto invoke its respective audit skill (audit-tests,audit-cohesion,audit-arch).prepare_issueto create a GitHub issue.ROUTE — Routing and Failure Handling
escalatefor that chain.doneandescalatestop steps.VALID — Validation
validate_recipewithout errors.load_recipeand executable via kitchen orchestration.