second-look
Skill1 starsChanged 3 months agoMITView on GitHub
Use before opening a pull request or merging work done in the current session, when the user asks for a fresh, independent, or second review, "a second pair of eyes", "have another agent check this", or wants to know whether the change actually does what they asked, not only whether it has bugs.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- arnonsang/skillstheir own version, first seen Nov 1, 2026
- MoonHuang0325/second-looktheir own version, first seen Sep 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- arnonsang/skills★ 4same name
- MoonHuang0325/second-look★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anger-translatorSkill
- cache-moneySkill
- codebase-memoirSkill
- codex-reviewSkill
- goalpostSkill
- grand-tourSkill
- identity-theftSkill
- relocate-sessionSkill
- right-stuffSkill
- rubicon-wordpress-version-labSkill
- secret-santa-generatorSkill
- showdownSkill
- star-chartSkill
- work-evidence-researchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
When a later message overrides an earlier one, FINAL REQUIREMENTS states only the current rule.
- Distinctive: line 38
Always use a new subagent.
- Very specific: line 47
After dispatching the reviewer, run /code-review on the same diff in this session.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Second look
An intent-first review by an agent that did not write the code. A bug hunt asks "is this code broken?" This asks "does this change do what the user asked, all of it, and only that?" and then runs the bug hunt as well.
The reviewer cannot see this conversation. Everything it knows about intent comes from the packet you write. The packet is the skill.
1. Write the reviewer packet
Build it from the whole session, not from memory of the first request. Every field is required; write "None" when a field is empty.
ORIGINAL ASK: <the user's first request, quoted>
CHANGES TO THE ASK: <each later clarification or reversal, quoted, with what it replaced>
FINAL REQUIREMENTS: <numbered list; the requirements as they stand now, after every change above>
OUT OF SCOPE: <what the user deferred or excluded, quoted; the reviewer must not report these as missing>
WHAT WAS BUILT: <files changed and why, one line each>
DECISIONS: <trade-offs made and the reason for each>
TESTS RUN: <exact command and result>
KNOWN GAPS: <what you are unsure of or did not finish>
DIFF: <how to see it, e.g. `git diff main...HEAD` plus untracked files>When a later message overrides an earlier one, FINAL REQUIREMENTS states only the current rule. The superseded version appears only under CHANGES TO THE ASK.
2. Dispatch a fresh reviewer
Always use a new subagent. Do not review in this context, even for a small diff: the point is a reader without your assumptions. If no subagent is available, say so and stop instead of reviewing your own work.
Give the reviewer the packet, read-only rules (no edits, no commits, no git writes), and these instructions:
- Intent review. For each FINAL REQUIREMENT: met or not met, with file:line evidence and, where possible, a command run against the code. Then: does any test assert behavior that contradicts a requirement? Does the change do anything no requirement asked for? Is it the smallest correct way? Take intent only from the packet; do not infer it from the diff. If the packet is ambiguous, report the ambiguity as a finding.
- Report each finding tagged
[intent], verified results kept apart from inferences.
3. Run the bug hunt
After dispatching the reviewer, run /code-review on the same diff in this session; its finders are separate agents that see only the diff. Tag its findings [bugs]. If /code-review is not available, tell the reviewer to add one independent correctness pass and tag those [bugs].
4. Report to the user
Merge the two sets of findings; when both found the same issue, keep it once and say both found it.
Lead with a verdict: ready, or not ready and why, in one sentence.
Then:
| # | Requirement | Met | Evidence |
Then findings, grouped:
- Blocker: a requirement not met, a test that asserts behavior contradicting a requirement, a likely regression, data loss, or a security issue.
- Non-blocker: a real but minor issue, or a test gap.
- Nit: worth knowing, never blocking.
Each finding carries its tag, the file and line, and why it matters. Anything listed in OUT OF SCOPE is not a finding. End with what the reviewer ran and what it only read.
The review changes nothing. Offer the fixes and wait for the user.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

