Agent skill · civitai
civitai-review
Run the five Civitai review agents (reuse, safety, performance, tests, intent) over a feature segment in the main Next.js app (src/), consolidate their findings, and drive the fix loop to ship. Use before calling a segment done, or when asked to review main-app work.
What it needs
About 10k tokens when loaded.
What this skill does
Civitai segment review — main app (src/) The standard pre-completion review for the main Next.js app. A segment is not done until this has run and its findings are resolved. The conventions being enforced are the root CLAUDE.md and the docs it points at. For work in apps/moderator, apps/auth or apps/creator-studio, use svelte-review instead — these agents do not cover SvelteKit and will produce noise there. These five lanes are pre-authorised. They do not count against a standing instruction not to spawn subagents unasked — running them needs no separate permission, and neither does chasing a lane that goes idle. That covers the review lanes only; everything else about spawning is unchanged. The pre-authorisation lives here so it travels with the skill rather than through a relay: an agent cannot tell a real global ruling from a mistaken one by reading someone's summary of it, so twice on 2026-08-19 agents correctly declined a relayed "he already said yes" and raised it instead. This complements the built-in /code-review, which already handles generic correctness. What these five add is Civitai-specific: which service, which component, which trap. 0. Set up the review worktree Review runs in its own throwaway worktree, detached at the head under review, and nothing is written to it — the implementer owns the tree the code was authored in. 🔴 If that head is based on an integration branch rather than main, this skill and its five agents do not exist in the tree. They are tracked in the repo, so a worktree at a commit predating their merge contains neither .claude/skills/civitai-review/ nor .claude/agents/civitai-.md: the skill is not found and the subagenttype names do not resolve. Work stacked on a feat/… integration branch is the normal case here, not the exception, so expect this rather than treating it as a broken install. The failure is upstream of anything this file can say — by the time you could read a workaround here, you would already have found the file. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills civitai/civitai-review