self-review

Reviews code diffs for architecture drift, secrets, stale code, and missing verification before handoff.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill self-review-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/vovanostm-public/multica/tree/main/.agents/skills/self-review
Command: npx skills add https://github.com/vovanostm-public/multica --skill self-review-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with hidden issues like architecture drift, leftover debug statements, leaked secrets, or untested paths. This Skill runs a structured self-review on your diff before handing work back, catching reviewable problems early. ## Core Features & Use Cases - Deterministic Diff Checks: Runs a shell script to surface changed files and detect unintended modifications or generated artifacts. - Architecture & Quality Audit: Verifies module role rules, state ownership, API compatibility, and flags commented-out code, stray logs, and obsolete paths. - Scoped Verification: Maps changed paths to targeted Turbo filters and Go test packages so you run only the narrowest relevant tests. - Use Case: After finishing a feature branch in the Multica monorepo, run this review to confirm no secrets leaked, no unrelated files changed, and the correct TypeScript and Go tests pass before opening a pull request. ## Quick Start Ask the agent to run the self-review workflow on the current diff and report what changed, which verifications ran, and any skipped checks with reasons.

Frequently Asked Questions about self-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review my code changes before creating a pull request?▼

Run the self-review workflow, which executes a deterministic diff check script, then audits scope, architecture, and code quality. It finishes with a report covering what changed, which verifications ran, and any skipped checks with reasons.

How to run only the tests affected by my changes?▼

Use the targeted verification command pnpm codex:targeted-verify, which maps changed paths to Turbo filters and go test packages. You can pass --base origin/main to set the comparison base or --skip-go to exclude Go tests.

What does the self-review check for in a diff?▼

It checks that only intended files changed, no secrets or private paths leaked, module role rules hold, state ownership is explicit, and no commented-out code or stray console.log statements remain. It also flags API compatibility concerns and duplicated web/desktop logic.

Can I use this review workflow outside the Multica repository?▼

The workflow is tailored to Multica conventions, including its Module Role Rule, Turbo filters, and scripts under scripts/codex. The general checklist ideas transfer, but the scripts assume the Multica monorepo layout.

Why does targeted verification skip some packages?▼

Targeted verification only runs tests mapped from changed file paths, so untouched packages are skipped by design. Use the --skip-go flag to exclude Go tests, or run the full make check when broader coverage is needed.