Agent skill · Design & Presentation

prior-art

Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill prior-art --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/prior-art/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Behavior Research how this codebase handles `$ARGUMENTS`. Explore the codebase thoroughly and report what you find. ### Step 1: Search Broadly Cast a wide net across the codebase. Use multiple search strategies: - **Grep for keywords** — search for terms related to the concern (e.g. for error reporting: `error`, `exception`, `rescue`, `Sentry`, `Bugsnag`, `notify`, `report`) - **Check common Rails locations** — initializers, middleware, concerns, base classes, config files, lib/ - **Check the Gemfile** — are there gems related to this concern? What do they tell you about the approach? - **Check application-level base classes** — `ApplicationController`, `ApplicationRecord`, `ApplicationJob` — these often set patterns that everything inherits - **Check for dedicated directories or files** — service objects, concerns, lib/ modules that handle this concern Don't stop at the first result. The goal is to find every place this concern is handled — the consistent pattern and the exceptions. ### Step 2: Check Git History For the key files involved in this concern: - `git log --oneline -10 <file>` to see recent changes - `git log --all --oneline --grep="<keyword>"` to find commits relate

What's inside
Steps it walks through
  1. Behavior
  2. Step 1: Search Broadly
  3. Step 2: Check Git History
  4. Step 3: Map What You Found
  5. Output Format
  6. Tone
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the prior-art skill do?

Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill prior-art --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going