dev-audit
Output style (plain words, no dashes, no hyphens)
Write everything this skill produces, files and messages alike, in plain simple language. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. A structural separator inside a template format other skills parse, such as the em dash in ## Phase 1 — <NAME>, is part of that format: reproduce it exactly, since changing it breaks the mirroring. Use short sentences, commas, or parentheses. Clear beats clever.
What this skill does
The durable follow through for code review. It ingests the current /dev-check review report for the requested task or change, then records the resulting findings in .konteksto/audit-register.md.
The review report remains the immutable evidence in .konteksto/reviews/. The audit register is the living checklist that stops the same finding being rediscovered and treated as new on every review.
Ownership
This skill owns the Issues table in .konteksto/audit-register.md. Create the file from templates/audit-register.md when it is first needed. /dev-qa may change an issue Status only from ready for QA to verified, or from ready for QA or verified to reopened, as the result of its own run.
/dev-qa owns the append only QA Runs table in the same file. Do not edit or delete its rows. Neither skill edits code, review reports, tests, or architecture documents.