by laulauraluo
Agent Skill for reviewing AI-written PRs in Claude Code, Codex, Copilot, Cursor and Gemini CLI: catch bugs, align context, own the sign-off.
# Add to your Claude Code skills
git clone https://github.com/laulauraluo/looks-good-to-aiGuides for using ai agents skills like looks-good-to-ai.
See how looks-good-to-ai compares with popular alternatives.
looks-good-to-ai is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by laulauraluo. Agent Skill for reviewing AI-written PRs in Claude Code, Codex, Copilot, Cursor and Gemini CLI: catch bugs, align context, own the sign-off. It has 93 GitHub stars.
looks-good-to-ai's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/laulauraluo/looks-good-to-ai" and add it to your Claude Code skills directory (see the Installation section above).
looks-good-to-ai is primarily written in Python. It is open-source under laulauraluo on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh looks-good-to-ai against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Formerly AI Code Review Triage
AI writes code faster than you can read it. Stop reading harder and review differently.
An Agent Skill that reviews AI-written pull requests by splitting "reading the code" into three separate jobs. Runs in Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, Antigravity, OpenCode, Windsurf, Cline, Roo Code, Kiro, Amp, Junie and Zed, and loads as plain context in Aider.
🇬🇧 · 🇨🇳 · 🇯🇵 · 🇰🇷 · 🇪🇸 · 🇧🇷 · 🇫🇷
Quick start · The idea · Install · Usage · Examples · How it works · Limits
Agent-written PRs pile up faster than anyone can review them line by line. Reading harder doesn't help much either: the code is tidy on the surface, so the real problems hide well enough to survive a careful read. "Just merge and roll back if it breaks" works technically, but a human still answers for the incident.
npx skills add laulauraluo/looks-good-to-ai
The skills CLI asks which agents to set up. Add -g to install for your user instead of this project, and -a <agent> to skip the question (-a claude-code, -a codex, -a github-copilot, -a cursor, …).
Or use the agent's own installer:
| Agent | Command |
|---|---|
| Claude Code | /plugin marketplace add laulauraluo/looks-good-to-ai then /plugin install looks-good-to-ai@looks-good-to-ai |
| Codex | codex plugin marketplace add laulauraluo/looks-good-to-ai then codex plugin add looks-good-to-ai@looks-good-to-ai |
| GitHub Copilot CLI | copilot plugin marketplace add laulauraluo/looks-good-to-ai then copilot plugin install looks-good-to-ai@looks-good-to-ai |
| Gemini CLI | gemini extensions install https://github.com/laulauraluo/looks-good-to-ai |
Then, in your agent:
Review this AI-generated PR before I merge it.
The skill loads on its own from a request like that. Most agents also take /looks-good-to-ai to call it by name; Codex uses $looks-good-to-ai. docs/agents.md has the command for each agent.
"Reviewing code" has always bundled three different jobs. That worked when code arrived slowly. At agent speed, each job needs its own process:
flowchart LR
PR([AI-written PR]) --> T{Step 0<br/>Triage<br/>risk tier}
T --> B["**1 · Catch bugs**<br/>fresh-context sub-agent<br/>+ tests / repro"]
B --> C["**2 · Align context**<br/>orders of magnitude<br/>history & neighbors<br/>requirement match"]
C --> S["**3 · Own the sign-off**<br/>explain · detect · undo<br/>scoped approval"]
S --> R([Review report])
| Job | Question | Who does it best |
|---|---|---|
| Catch bugs | Is the code wrong? | Machines, with an independent second pass |
| Align context | Is this the right change for this product, today? | A human, checking angles the diff can't show |
| Own the sign-off | Will I put my name on this? | The approver, with an explicit scope |
Low-risk PRs only run Step 1. Medium-risk PRs run Steps 1 and 2. High-risk PRs (production behavior, data, security, money) run all three.
A PR changes
SESSION_TIMEOUT = 30to30000and drops one line of unit conversion. Tests pass. The code is clean. A line-by-line reader approves it in 30 seconds.
- Step 1 has a fresh-context sub-agent add a boundary test. Result: sessions now expire after 30 seconds.
- Step 2 checks history and callers. The same change was reverted once before, the mobile client hard-codes the old value, and the request was only for "remember me" users while the diff changes everyone.
- Step 3 blocks the approval. Nobody can explain what the PR actually does.
Full run: examples/session-timeout-walkthrough.md
The skill is the folder skills/looks-good-to-ai/. Every agent below loads it unchanged; only the folder differs. docs/agents.md has the full table with every folder each agent reads, the way each agent calls a skill, and a link to each agent's own documentation.
| Agent | skills CLI | Or copy the folder to (user · project) |
|---|---|---|
| Claude Code | -a claude-code |
~/.claude/skills/ · .claude/skills/ |
| Codex | -a codex |
~/.agents/skills/ · .agents/skills/ |
| GitHub Copilot | -a github-copilot |
~/.copilot/skills/ · .github/skills/ |
| Cursor | -a cursor |
~/.cursor/skills/ · .cursor/skills/ |
| Gemini CLI | -a gemini-cli |
~/.gemini/skills/ · .gemini/skills/ |
| Antigravity | -a antigravity |
~/.gemini/config/skills/ · .agents/skills/ |
| OpenCode | -a opencode |
~/.config/opencode/skills/ · .opencode/skills/ |
| Windsurf | -a windsurf |
~/.config/devin/skills/ · .devin/skills/ |
| Cline | copy by hand (why) | ~/.cline/skills/ · .cline/skills/ |
| Roo Code | -a roo |
~/.roo/skills/ · .roo/skills/ |
| Kiro | -a kiro-cli |
~/.kiro/skills/ · .kiro/skills/ |
| Amp | -a amp |
~/.config/agents/skills/ · .agents/skills/ |
| Junie | -a junie |
~/.junie/skills/ · .junie/skills/ |
| Zed | -a zed |
~/.agents/skills/ · .agents/skills/ |
| Aider | — | read: in .aider.conf.yml (how) |
| Continue | — | Unverified; load as a rule (how) |
Clone the repository once and copy the skill folder into the agent's folder from the table, so that SKILL.md ends up at <folder>/looks-good-to-ai/SKILL.md:
git clone https://github.com/laulauraluo/looks-good-to-ai.git
cp -r looks-good-to-ai/skills/looks-good-to-ai ~/.claude/skills/
Swap ~/.claude/skills/ for any other folder in the table. For a project install, commit the copied folder so your team gets it too.
A reusable workflow runs the skill on each pull request and posts the report as a comment. Setup takes three steps: docs/github-action.md.
Inside Claude Code:
/plugin marketplace add laulauraluo/looks-good-to-ai
/plugin install looks-good-to-ai@looks-good-to-ai
Ask your agent something like:
You get a report like this (from the invented timeout example):
## Extend session lifetime for "remember me" · Risk: High
### 1. Bugs (independent fresh-context review)
- [CONFIRMED] auth/session.py:3 — unit conversion dropped; sessions expire after 30 s. Repro: test_session_expires_after_timeout
### 2. Context
- Magnitudes: SESSION_TIMEOUT 30 → 30000 (comment says min, code treats as ms) — suspicious
- History / neighbors: reverted once before (a1b2c3d); mobile/src/config.ts hard-codes 30 min
- Requirement match: asked for remember-me users only; diff changes everyone
### 3. Sign-off
- Detection: login-rate and 401-rate alerts · Rollback: config revert
- Recommendation: request changes
- Verification scope: verified units and callers; did not load-test
<sub>Reviewed with [Looks Good to AI](https://github.com/laulauraluo/looks-good-to-ai)</sub>
The last line credits the skill when you paste the report into a PR. Ask the agent to leave it out if you don't want it.
Here's the diff for PR #482. Cursor wrote it to raise our retry count from 3 to 10 on the payments client. Tests pass. Can I approve it?
Copilot opened a PR that only fixes typos in docs/ and the README. Do I need the full review process?
I wrote this change with you in this session. Now review it before I merge.
Both walkthroughs are invented scenarios that follow one PR through every step.
| Walkthrough | W