stark-review

Reviews GitHub pull requests across triage-selected domains using a single configurable LLM agent.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/21StarkCom/stark-skills --skill stark-review-21starkcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stark-review
Source: https://github.com/21StarkCom/stark-skills/tree/main/runtime-overrides/codex/skill/stark-review
Command: npx skills add https://github.com/21StarkCom/stark-skills --skill stark-review-21starkcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests thoroughly requires checking many concerns — architecture, security, test coverage, spec conformance — which is slow and inconsistent when done manually. This Skill automates single-agent PR review across triage-selected domains while keeping posting and code changes behind explicit authorization gates. ## Core Features & Use Cases - Domain-based PR review: Dispatches one LLM agent (claude, codex, or gemini) across selected review domains such as security, architecture, and test coverage, with per-domain defaults configurable in config.json. - Safe-by-default authorization: Reviews are read-only unless the user explicitly passes --post to publish findings and --fix to run the fix loop that edits, tests, commits, and pushes to the PR branch. - Classified findings and fix loop: The TypeScript dispatcher classifies findings as fix, noise, or false positive, optionally fixes medium+ issues, verifies with a trusted test command, and records round history. - Use Case: Run a fast security-and-test-coverage pass on PR #42 with --domains security,test-coverage, review the findings locally, then re-run with --post --fix to publish the review and push verified fixes. ## Quick Start Ask the assistant to review pull request 42 in the current repository using the stark-review skill with default triage-selected domains and no posting.

Frequently Asked Questions about stark-review

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

FAQPage Schema
How do I review a GitHub pull request with an LLM agent?▼

Run the skill with a PR number, and it detects the PR via the GitHub CLI, provisions an isolated worktree, and dispatches one agent across triage-selected review domains. By default the review is read-only and results are reported locally without posting.

How do I review only specific domains like security or test coverage?▼

Pass --domains with comma-separated slugs, for example --domains security,test-coverage, for a surgical review. Alternatively use --quick to run the small fast domain subset defined as quick_domains in config.json.

Can I choose between Claude, Codex, and Gemini for code review?▼

Yes, pass --agent claude, codex, or gemini to force one agent across every domain. Without it, the domain_agents mapping in config.json selects the default agent per domain, resolved through the repo, org, and global config hierarchy.

Does the review automatically post comments or push fixes to GitHub?▼

No. Posting requires the explicit --post flag, and the fix loop requires both --post and --fix. A plain review request always runs with dry-run and no-fix-loop safeguards, so nothing is published or committed without consent.

What happens when reviewing a fork pull request?▼

Fork PRs are review-only by default and never run the fix loop. Pushing fixes to a fork requires maintainerCanModify, or both the --allow-untrusted-fix-loop CLI flag and untrusted_fix_loop=true in config.

Why does the fix loop skip even when fixes are authorized?▼

The loop soft-skips when no test command resolves, when the fork lacks push permission, or when --no-fix-loop was passed. The receipt records the skip reason such as no_test_command or fork_no_mcm in its audit log.