New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review Brief

by every-app in every-app/open-seo

Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff.

MITAuto-check passedMarketing & SEO

Install Review Brief

skills CLI
$ npx skills add every-app/open-seo --skill review-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install every-app/open-seo review-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-brief .claude/skills/review-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-brief
GitHub stars
23k
Token cost
~1.2k tokens
SKILL.md length
730 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff.

  • Works in 5 steps: Get the diff (git log --oneline… → Find the invariant core: what was… → Classify every hunk. Anything matching… → …
  • The user asks how do I review this
  • SKILL.md covers Process, Crucial code criteria, Layout and Rules, plus 1 more section
  • Calls git

What it does

Review Brief is an agent skill from every-app/open-seo. Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff. Use when the user asks "how do I review this", "summarize the changes", "what should I look at", or wants to understand a PR in under two minutes.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO. The repository describes itself as: Open source alternative to Semrush and Ahrefs. The licence is MIT.

When your agent uses it

  • The user asks how do I review this
  • Summarize the changes
  • What should I look at
  • Wants to understand a PR in under two minutes

Example prompts

  • “how do I review this”
  • “summarize the changes”
  • “what should I look at”
  • “/review-brief”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Get the diff (git log --oneline main..HEAD, git diff --stat main..HEAD) and
  2. Find the invariant core: what was broken, what is true now. One sentence.
  3. Classify every hunk. Anything matching the crucial criteria below goes into
  4. Write the brief in the layout below. Every line number cited must be verified
  5. Run a second agent as a reviewer of the CODE, not the prose: "what is wrong,

What it can do on your machine

Read from SKILL.md and the folder at commit 89e5a00. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Brief loads about 1.2k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 730 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from every-app/open-seo at commit 89e5a00, republished under its MIT licence (© every-app). 730 words, ~1,181 tokens.

Download SKILL.mdSave it as .claude/skills/review-brief/SKILL.md (or your agent's skills folder).
name
review-brief
description
Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff. Use when the user asks "how do I review this", "summarize the changes", "what should I look at", or wants to understand a PR in under two minutes.
metadata.internal
true

Review brief

The reader will not read the diff. They will skim for 30 seconds, then read only the code that could hurt them. Optimize for that.

Process

  1. Get the diff (git log --oneline main..HEAD, git diff --stat main..HEAD) and read every non-trivial changed file in full.
  2. Find the invariant core: what was broken, what is true now. One sentence.
  3. Classify every hunk. Anything matching the crucial criteria below goes into the code section verbatim. Everything else gets one table row or is folded.
  4. Write the brief in the layout below. Every line number cited must be verified against the working tree.
  5. Run a second agent as a reviewer of the CODE, not the prose: "what is wrong, overstated, or missing?" Fix real bugs before delivering, and say you did.

Crucial code criteria

A hunk is crucial and must be shown as code if it touches any of:

  • Schema. Drizzle tables, columns, indexes, migrations, Zod schemas at a trust boundary, MCP tool input or output schemas.
  • Database writes. New or changed INSERT/UPDATE/DELETE, conditional WHERE clauses, anything that runs inside a workflow step or a cron.
  • Security. Auth checks, scope or org or project gating, secrets, external calls with credentials, anything that fails open.
  • Core logic. The branch or expression that decides the outcome the bug was about: a status assignment, a validation gate, a ranking comparator, a retry or timeout policy.
  • Jank. Anything you would be embarrassed to defend in review. String-matching a vendor error message to pick UI copy. A regex standing in for a parser. A hard-coded lookup table. A console.warn where a metric belongs. A swallowed catch. A magic timeout. A DB read added to work around a missing parameter. A fallback that quietly changes behaviour. Show it, name it as jank in the sentence above, and say whether it is acceptable for now or should block.

Show each as 5 to 20 lines, trimmed to the decision, with one sentence above saying what to notice and one line below naming the failure mode if it is wrong. Three to six excerpts is normal. If there are more than six, the PR should probably be split; say so.

Show full SKILL.md (364 more words)Show less

Layout

One sentence stating what was broken and what is true now.

Before / after diagram. One ASCII flow, two columns, showing the user-visible path. Boxes are steps, arrows are what flows. Label the bug locations.

The code that matters. The crucial excerpts, in reading order by risk. This section is the point of the brief. Do not defer it to a follow-up.

Everything else, in one table. Sorted by risk:

| # | File | What it does | The one thing to check |

One row per remaining meaningful change. Fold registrations, renames, formatting, and fixtures into a single final row.

What does NOT exist. Bullets naming the things a reader would assume were added and were not: no migration, no new dependency, no change to a persisted shape, no new auth path.

Decisions you might disagree with. Two to four bullets. Each: the choice, the alternative, the cost of the choice. No defence longer than one sentence.

Status table. Whatever numbers gate the merge: tests, dry-run counts, "applied to prod: No".

Try it in two minutes. The two or three commands that exercise the change.

Branch state. Commits, pushed or not, PR link or "no PR yet".

Rules

  • No paragraph over two sentences anywhere.
  • Bold the first few words of every bullet so the list skims by its openers.
  • Tables for anything with three or more parallel facts.
  • Code goes in fences, never in prose. Name a file only when the reader has to go there.
  • Cut history, rejected alternatives, and migration narrative unless asked.
  • Never simplify into inaccuracy. A detail that changes what the reader would do stays, as one line.
  • Under 600 words of prose. Code excerpts and tables do not count.

Anti-patterns

  • A numbered walkthrough with paragraphs per stop and a "Check:" paragraph.
  • Describing a WHERE clause, an auth check, or a status expression in words instead of showing it.
  • Hiding jank in a "decisions you might disagree with" bullet. If it is in the code, show the code.
  • Saving the code for "want me to show you the code?" The reader asked for a review brief; the code is the brief.
  • A draft PR description inline. Put it in a file and link it.

© every-app, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/review-brief of every-app/open-seo.

Open the folder on GitHubat commit 89e5a00

Compare with similar skills

Review Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Brief this skillevery-app/open-seo23k—~1.2kAutomated safety check: PassMIT
Geo Fundamentalswasp-lang/wasp19k9 repos~861Automated safety check: PassMIT
Ab Testingcoreyhaines31/marketingskills54k3 repos~3.1kAutomated safety check: PassMIT
Hreflang and International SEOAgriciDaniel/claude-seo19k5 repos~3.4kAutomated safety check: PassMIT
Referralscoreyhaines31/marketingskills54k2 repos~2.6kAutomated safety check: PassMIT
SEO GeoReScienceLab/opc-skills1.8k4 repos~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Geo Fundamentals

    wasp-lang/wasp

    Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

    19k GitHub starsUsed in 9 repos~861 tokens
    Marketing & SEOAuto-check passed

  • Ab Testing

    coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    54k GitHub starsUsed in 3 repos~3.1k tokens
    Marketing & SEOAuto-check passed

  • Hreflang and International SEO

    AgriciDaniel/claude-seo

    Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.

    19k GitHub starsUsed in 5 repos~3.4k tokens
    Marketing & SEOAuto-check passed

  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.6k tokens
    Marketing & SEOAuto-check passed

  • SEO Geo

    ReScienceLab/opc-skills

    SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub starsUsed in 4 repos~2.1k tokens
    Marketing & SEOAuto-check passed

  • Ad Creative

    LeoYeAI/openclaw-marketing-skills

    When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.

    1k GitHub starsUsed in 8 repos~3.4k tokens
    Marketing & SEOAuto-check passed

More from every-app/open-seo

All 19 skills in this repo

  • Evaluate Skill

    every-app/open-seo

    Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.

    23k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check: notes

  • Create Repo Skill

    every-app/open-seo

    Create or update a skill in this repository the right way — canonical home in .agents/skills, internal-vs-public marking, symlink mirroring into .claude/skills, and public docs registration for…

    23k GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

  • Deslop

    every-app/open-seo

    Remove AI writing patterns from prose so it reads like a person wrote it.

    23k GitHub stars~602 tokensUpdated 2 days ago
    Auto-check passed

  • Observability Triage

    every-app/open-seo

    Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically.

    23k GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check passed

  • Papercuts

    every-app/open-seo

    Log genuine, recurring repository friction to .agents/PAPERCUTS.md — confusing setup, a flaky repo command or script, a misleading in-repo error, stale generated files, or a non-obvious gotcha that…

    23k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

  • Simple Issue Description

    every-app/open-seo

    Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior.

    23k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Review Brief

What does Review Brief do?

Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff. Review Brief is an agent skill from every-app/open-seo. Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff.

When should I use Review Brief?

Review Brief fits situations like: the user asks how do I review this; summarize the changes; what should I look at; wants to understand a PR in under two minutes.

How do I install Review Brief in Claude Code?

Run `npx skills add every-app/open-seo --skill review-brief -a claude-code`. Or copy the skill folder (.agents/skills/review-brief in every-app/open-seo) into .claude/skills/review-brief in your project. Claude Code loads it when a task matches its description.

How do I install Review Brief in Codex?

Run `npx skills add every-app/open-seo --skill review-brief -a codex`. Or copy the skill folder (.agents/skills/review-brief in every-app/open-seo) into .agents/skills/review-brief in your project. Codex loads it when a task matches its description.

Can I use Review Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add every-app/open-seo --skill review-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-brief, .gemini/skills/review-brief, .github/skills/review-brief and .opencode/skills/review-brief in your project.

What does Review Brief need to run?

Going by SKILL.md and its folder, Review Brief needs the command-line tools its instructions call (git).

Does Review Brief access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Brief use?

Review Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Brief use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review Brief?

Skills that share tags, products or a category with Review Brief: Geo Fundamentals (wasp-lang/wasp, 19k stars), Ab Testing (coreyhaines31/marketingskills, 54k stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 19k stars) and Referrals (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Brief?

every-app (a GitHub organization) maintains it in every-app/open-seo, which has 22,922 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.

Source: every-app/open-seo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.