Carly Code Review
Comprehensive code review using 7 parallel specialized sub-agents (correctness, security, performance, simplicity, UX, codebase integration, documentation). Every finding needs a concrete failure scenario; Critical/Warning findings are then challenged by adversarial refuter agents before they reach the report. Repos can add their own reviewers via an `Extra reviewers:` list in CLAUDE.md. Use when reviewing code changes, pull requests, or local diffs. Supports local git diff (no arguments) or GitHub PR (pass PR number or URL as argument).
Install
/plugin marketplace add carlymr/carlys-claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add carlymr/carlys-claude-skills --skill carly-code-reviewgit clone --depth 1 https://github.com/carlymr/carlys-claude-skills.git /tmp/carlys-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/carlys-claude-skills/skills/carly-code-review ~/.claude/skills/carly-code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review Orchestrator Coordinate a code review by delegating to specialized reviewer sub-agents in parallel, then synthesize their findings into a single actionable report. ## Step 1 — Get the diff ### Local changes (no arguments) Review everything on this branch — commits, staged, unstaged, and untracked files — against where the branch started. 1. **Find the default branch** (don't assume `main`). Try in order until one works: - `git symbolic-ref --short refs/remotes/origin/HEAD` — prints `origin/<default-branch>`; fails when `origin/HEAD` was never set (common for repos created with `git init` + `git remote add`) - `gh repo view --json defaultBranchRef --jq .defaultBranchRef.name` - `git rev-parse --verify origin/main`, then `origin/master` 2. **Diff against the merge base**, not the default branch's current tip — the tip would also show every change that landed there since the branch started, reversed. This diff covers committed, staged, and unstaged changes: ```bash git merge-base HEAD origin/<default-branch> git diff <merge-base> git diff <merge-base> --name-only ``` 3. **Find untracked files**, which `git diff` doesn't show: ```bash git status --porcelain --untracked-files=all ``` Treat the full contents of `??` entries as added code: include them in the file list and have reviewers Read them. ### GitHub PR (PR number or URL in `$ARGUMENTS`)
Details
- Skill name
carly-code-review- Repository
- carlymr/carlys-claude-skills
- Path
skills/carly-code-review/SKILL.md- Repo updated
- 4 October 2026
FAQ
What does the Carly Code Review skill do?
Comprehensive code review using 7 parallel specialized sub-agents (correctness, security, performance, simplicity, UX, codebase integration, documentation). Every finding needs a concrete failure scenario; Critical/Warning findings are then challenged by adversarial refuter agents before they reach the report. Repos can add their own reviewers via an `Extra reviewers:` list in CLAUDE.md. Use when reviewing code changes, pull requests, or local diffs. Supports local git diff (no arguments) or GitHub PR (pass PR number or URL as argument).
How do I install the Carly Code Review skill?
Claude Code plugin: /plugin marketplace add carlymr/carlys-claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Carly Code Review popular?
It lives in carlymr/carlys-claude-skills, which has 9 GitHub stars and 0 forks.
Related skills
Carly Product Req
9carlymr/carlys-claude-skills
Co-author a lightweight product requirements document through structured conversation. Guides non-technical teammates through problem statement, users, goals, success signals, and open questions — producing a short doc (~1 page) that's ready to hand off for a tech spec. Use when writing product requirements, a PRD, feature brief, or scoping a new product idea.
Carly Tech Spec
9carlymr/carlys-claude-skills
Co-author a technical design specification through structured conversation. Guides you through problem statement, goals, current state, proposed solution, alternatives, risks, and milestones — with a fixed template and coaching at each step. Use when writing a tech spec, design doc, technical proposal, or RFC.
Push Check
10charlie947/skills-for-everyone
Check everything before work goes to GitHub, then push it. Runs the repo's own checks, a sweep for leaked keys, personal paths, oversized files and dead links, a second Claude reading the changes cold, and a fresh-copy rehearsal of what a new user does first. Pushes only after two clean passes in a row, then drafts the short note to send people, if there is anything for them to do. Use when the user says "push", "push this", "ship it", "put it on GitHub", "release", "send it to them", "is it ready to push", or is about to share a repo other people will download.
Changelog Newsletter
9tomique34/claude-skill-creator
Transform technical changelog entries into user-friendly newsletter content for email, blog posts, and release notes. Use when converting CHANGELOG.md files, git commit logs, or release notes into customer-facing communications.
Repo Wiki Detect
9boweneos/repo-wiki-agent-skills
Detect code changes since last wiki update using git diff. Identifies added, modified, deleted, and renamed files to determine which documentation pages need updates.
Navigating Github to Konflux Pipelines
9konflux-ci/agent-plugins
Use when GitHub PR or branch has failing checks and you need to find Konflux pipeline information (cluster, namespace, PipelineRun name). Teaches gh CLI commands to identify Konflux checks (filter out Prow/SonarCloud), extract PipelineRun URLs from builds and integration tests, and parse URLs for kubectl debugging.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.