← ClaudeAtlas

fullstack-reviewerlisted

This skill should be used when the user asks to review code, review my changes, code review, review this project, check code quality, security review, find bugs, or requests a comprehensive, structured code review covering both frontend and backend.
AruNi-01/atmos · ★ 2 · Code & Development · score 69
Install: claude install-skill AruNi-01/atmos
# Fullstack Code Reviewer Perform a comprehensive, senior-engineer-level code review for the current project changes. This skill is **project-agnostic** — it works with any language, framework, or tech stack. Analyze git changes, detect issues across both frontend and backend code, and output a structured Markdown report to the specified file path. ## Atmos Review Session Integration When the prompt contains a `<review-agent-run>` block, the session may target either a **workspace** (isolated git worktree) or a **project** (the project's main checkout). The reviewer flow is target-agnostic — it only needs the `session`, `current_revision_guid`, and `run` GUIDs from the block — but respect the target kind if you need to read repo state (target kind is visible in the output of `atmos review session-show --session <session_guid>`). Use the run/session metadata to create one inline comment per concrete finding: ```bash atmos review create-comment \ --session <session_guid> \ --revision <current_revision_guid> \ --file <path> \ --side new \ --start-line <line> \ --end-line <line> \ --title "<short title>" \ --run <run_guid> \ --body-stdin <<'EOF' Severity: P1 Issue: ... Suggestion: ... EOF ``` Prefer `--body-stdin` (or `--body-file <path>`) for multi-line bodies; `--body "..."` is only for short single-line text. After the review is complete, call: ```bash atmos review set-status --run <run_guid> succeeded --summary-stdin <<'EOF' <one-paragraph summary> EO