requesting-code-review

Dispatches adversarial subagent code reviews on git diffs and processes findings by severity.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/dariovr1/sixth-sense --skill requesting-code-review-dariovr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/dariovr1/sixth-sense/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/dariovr1/sixth-sense --skill requesting-code-review-dariovr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code that passes type checks, linting, and builds can still ship with edge-case bugs and design flaws, and self-review by the same agent that wrote the code carries inherent bias. This Skill enforces a structured, independent review pass before merging, with severity-ranked findings and disciplined feedback handling. ## Core Features & Use Cases - Risk-Triage Diff Review: Computes BASE_SHA/HEAD_SHA against the repo's actual default branch and dispatches the dylan-dog skill in Hunting mode, which partitions the diff by risk instead of applying one uniform review pass. - Degraded and Snapshot Modes: Falls back to a snapshot review of session-modified files when no git repository exists, or to an explicit self-review when subagent dispatch is not viable, always labeling the review mode in output. - Opus Second Opinion: Optionally dispatches a read-only opus-review pass after the primary review and merges its findings into the same Critical/Important/Minor report. - Use Case: After implementing a feature spanning a dozen files, run this Skill before merging to main; it triages the diff, hunts edge cases per file, and returns confirmed findings you fix one at a time with technical reasoning rather than performative agreement. ## Quick Start Request a code review of my current branch's changes before merging into the default branch.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a code review before merging a feature branch?

Run this Skill after completing a feature: it computes the merge-base and HEAD SHAs against your repo's actual default branch, then dispatches the dylan-dog skill to triage the diff by risk and hunt edge cases. Findings come back ranked Critical, Important, and Minor.

How does risk-based diff triage work in code review?

The dylan-dog skill partitions the diff by risk so high-risk hunks get deep edge-case hunting while low-risk changes skip the full-cost review. This avoids both vague single-pass reviews and uniform deep review of trivial changes.

Can I get a code review without a git repository?

Yes. When git rev-parse fails, the Skill switches to snapshot mode: it lists every file created or modified in the session and dispatches dylan-dog-hunter directly on those files, skipping triage since there is no diff to partition.

What should I do when I receive code review feedback?

Follow the six-step loop: read fully, restate the requirement, verify against the codebase, evaluate technical soundness, respond with reasoning, then implement one item at a time. Fix Critical issues immediately and push back with technical arguments when a finding is wrong.

When is the Opus second opinion review skipped?

The Opus pass runs by default but is skipped entirely when .sixth-sense/model-preferences.md explicitly sets opus-review to false. If the setting is absent, the review runs, and its findings merge into the same severity-ranked report.