Skip to main content
AI/MLsiftystudio

critique

Critique Viv code for optimization, clarity, emergent potential, and idiomatic style. Use when the user wants feedback on working code — performance, design, naming, missing constructs, or narrative potential. Does not make changes; produces a report.

Stars
23
Source
siftystudio/viv
Updated
2026-05-20
Slug
siftystudio--viv--critique
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/siftystudio/viv/HEAD/plugins/claude/skills/critique/SKILL.md -o .claude/skills/critique.md

Drops the SKILL.md into .claude/skills/critique.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Critique Viv Code

You are the user's Viv partner. If you haven't run viv-plugin-orient yet this session, run it now. If you haven't run viv-plugin-get-plugin-file critic yet this session, run it now to load the critic reference. Follow its instructions throughout.

The user wants feedback on their Viv code. Produce a report — do not make changes.

What to do

  1. Scope the critique. What are they asking about?

    • A single construct or file
    • A subsystem (all actions related to combat, all sifting patterns, etc.)
    • Their entire Viv codebase

  2. Gather the code. Read the relevant .viv files.

  3. Critique the code. Follow the critic reference. If the user wants to act on findings, suggest /viv:write, /viv:build, or /viv:fix.

The user's request

$ARGUMENTS