Devrites audit

Skill ViktorsBaikers/DevRites/pack/.claude/skills/devrites-audit

Stop your AI from shipping half-baked code. A disciplined senior-engineer workflow for Claude Code (spec, vet, build, prove, review, seal, ship) that keeps each feature's state on disk, catches spec drift mid-build, gates every phase on your project's principles, and refuses to claim "done" without proof.

Install

npx -y skills add ViktorsBaikers/DevRites --skill devrites-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Read-only feature audit on security/perf/simplify: auth trust boundary, injection, secrets, hot-path, payload-size, perf budget, Chesterton delete/cleanup. Use when auditing one axis. Not for writes.

SKILL.md

2.3 KB, as published. Nobody here has run it

devrites-audit: read-only audit dispatch

Dispatch one fresh-context, read-only review axis for the active feature. The caller decides how to use the report; this skill never edits.

Axis

Argument	Role	Discipline
`security`	`devrites-security-auditor`	trust boundaries, OWASP, secrets, dependencies
`perf`	`devrites-performance-reviewer`	measure-first hot paths, N+1, payload/bundle and stated budgets
`simplify`	`devrites-simplifier-reviewer`	behavior-preserving deletion/simplification; Suggestion/Nit/FYI only

If no axis is supplied, infer only when intent is unambiguous; otherwise the root asks the human before dispatch.

Gather and dispatch

Resolve .devrites/ACTIVE; require spec.md and touched-files.md.
Follow the universal file-backed packet, result, budget, retry, and fresh-context dispatch ladder in agents.md.
Set payload.type: review-findings; include spec.md, decisions.md when present, evidence.md for performance, touched-files.md, and the immutable diff.
Objective: derive expected behavior independently, apply the role's documented discipline, and return one labeled finding per line with file:line.
Await, validate, and pass the role payload to the caller verbatim. The root reconciles and decides what to accept.

Use one dispatch per axis. If several axes are requested, use separate packets with no cross-pollination and the shared maximum of three concurrent read-only roles.

Fallback and scope

Use the capability ladder. If no safe fresh-context rung preserves the role's read-only boundary, stop for HITL. Use these role contracts:

.claude/agents/devrites-security-auditor.md
.claude/agents/devrites-performance-reviewer.md
.claude/agents/devrites-simplifier-reviewer.md

Stay inside the active feature. Critical findings block seal; simplification never changes behavior.