← ClaudeAtlas

deepreviewlisted

Perform an exhaustive, multi-perspective review of pending changes for correctness, security, maintainability, architecture, and stack compliance, then apply confirmed in-scope fixes. Use for deep, high-risk, release, or pre-merge reviews.
NomadicDaddy/aidd · ★ 1 · Code & Development · score 60
Install: claude install-skill NomadicDaddy/aidd
# Deep Review Perform an exhaustive review of the requested change set, reconcile independent perspectives, and apply confirmed in-scope fixes directly. Prefer `review` for a routine focused pass. ## Usage ``` deepreview [boundary] [focus] ``` - Zero args → review the current unit of work using the resolution rules below. - `[boundary]` → base ref, commit, commit range, or path. - `[focus]` → optional review emphasis stated in plain language. ## Inputs Accept an optional base ref, commit range, path, or focus area. When none is supplied, review all tracked and untracked changes in the current repository. A clean working tree does not mean there is nothing to review. When no uncommitted work exists, review the commits that produced the change under review: the ones belonging to the unit of work this session was launched for, identified from the newest `.aidd/CHANGELOG.md` entry, the most recently touched `.aidd/features/*/feature.json`, and recent commit times. Fall back to the branch's upstream or default-base range only when that fails to identify them, and only for the part of it that is plausibly the same unit of work — a long-lived branch routinely sits many commits ahead of its upstream, and unrelated accumulated history is out of scope. State the resolved boundary in the report, and report "nothing to review" only when both the working tree and those commits are empty. ## Workflow ### 1. Establish scope and rules 1. Confirm the repository root and read all app