independent-review

Solid

Before 'ship it', a deploy or release, for 'an independent review', and after each fix until a round is clean: a fresh reviewer that never saw the build.

Code & Development 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Independent review — the gate before a change ships **The session that wrote the code never clears it.** A fresh reviewer that never saw the build reads the change for what would block or break it. That separation applies at every size: a one-line fix that ships gets a short round, never no round. Inside a phase, it joins the phase's series (§ When). **The tool is optional; the review is not.** The wrapper picks the first installed CLI in this order. Run `python <skill dir>/scripts/review.py --check` to see which. - A fresh Codex session in a read-only sandbox excludes user config and its MCP servers, execpolicy rules, connected apps, plugins, tool suggestions, web search, image generation, memory and saved sessions. A flag disables hooks. Repository and `CODEX_HOME` `AGENTS.md`, bundled skills, agent tools and administrator additions remain. Name them in the report (`codex-agents` § Reviewer lists the boundaries). - A fresh headless Claude Code session uses read-only tools. It has no settings, hooks, plugins, MCP servers, auto-memory or saved session, starting from the repository and brief alone. - Grok runs with read-only tools. Its memory, managed MCP servers, and Claude, Cursor and Codex compatibility, including session reading, are off for the run. The wrapper reads whatever still loads from `grok inspect` and prints it for the report. In a trusted folder, that includes project instructions and a gitignored `CLAUDE.local.md`. A review worktree of the snapshot does n...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

review

Review changed code for correctness and quality, then apply the project-specific checks Claude Code's built-in reviewer does not know about.

1 Updated today
djnsty23
Code & Development Listed

independent-review-loop

Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer that fails differently from the authors, run to clean — distinct from the recursive-refinement ladder. Invoked by the team lead from the unified pre-ship gate (code-mode and /swarm:refine) after the ship steps.

85 Updated 3 months ago
DheerG
Code & Development Listed

ship-check

Run the full post-implementation review pipeline: PR review, fresh-eyes, code-quality, test-audit, bug-check and pr-monitor. Phases 1-5 run as dedicated agent types (ship-check plugin) with their source-declared skills — genuine fresh eyes with no inherited context. Phase 6 (pr-monitor) runs inline for user interaction. A report-only design pass reads the whole PR after Phase 5, and again in Phase 6 when code changed since. When a change touches a committed MCP tool list, the tool-definition reviewer runs after Phase 5 and again before each merge-ready verdict. A dedicated security auditor checks complete affected security surfaces after design/tool-definition triage and before pushing. Use when asked to "ship check", "review pipeline", "full review", "run all reviews", or after implementation is complete and ready for review. NOT for: single-dimension review (use the individual skill), quick CI check (use pr-monitor), or post-merge cleanup (use land-task).

1 Updated 4 days ago
aliasunder