Skip to content

feat: add project-scoped full-audit recipe (.autoskillit/recipes/full-audit.yaml) #686

@Trecek

Description

@Trecek

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_testsrun_skill /autoskillit:audit-tests on the target branch
  • audit_cohesionrun_skill /autoskillit:audit-cohesion on the target branch
  • audit_archrun_skill /autoskillit:audit-arch on the target branch

Wave 2: Validations (parallel, after respective audit completes)

  • validate_audit_testsrun_skill /autoskillit:validate-audit {audit-tests report path}
  • validate_audit_cohesionrun_skill /autoskillit:validate-audit {audit-cohesion report path}
  • validate_audit_archrun_skill /autoskillit:validate-audit {audit-arch report path}

Wave 3: Issue creation (parallel, after respective validation completes)

  • issue_audit_testsprepare_issue from the validated audit-tests report
  • issue_audit_cohesionprepare_issue from the validated audit-cohesion report
  • issue_audit_archprepare_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

  • .autoskillit/recipes/full-audit.yaml exists and passes validate_recipe
  • Recipe accepts a branch ingredient (required)
  • Three audits run in parallel (wave 1)
  • Three validate-audit steps run in parallel after their respective audit (wave 2)
  • Three prepare-issue steps run in parallel after their respective validation (wave 3)
  • Any single-chain failure routes to escalate without blocking sibling chains
  • Recipe produces three GitHub issues from validated audit reports
  • Recipe can be loaded and executed via load_recipe + kitchen orchestration

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestrecipe:implementationRoute: proceed directly to implementationstagedImplementation staged and waiting for promotion to main

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions