agentleFS
Vlor999Vlor999/pr-radar/CLAUDE.md

pr-radar

CLAUDE.md0 starsChanged 13 days agoMITView on GitHub

Tauri v2 desktop app + React 19 + Vite + Tailwind v4 + shadcn (preset b7ClNF3YW, base-ui, cn imported from "cn"). Strict TypeScript, prettier semi: false. No backend: direct calls to api.github.com through @tauri-apps/plugin-http.

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never print or commit ~/.tauri/pr-radar.key or its password (CI secrets TAURI_SIGNING_PRIVATE_KEY*).

    line 16
  2. Very specific:

    Every feature: local browser demo (skill demo, npm run demo → localhost:1420, mocked data) and explicit user validation before …

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

PR Radar

Tauri v2 desktop app + React 19 + Vite + Tailwind v4 + shadcn (preset b7ClNF3YW, base-ui, cn imported from "cn"). Strict TypeScript, prettier semi: false. No backend: direct calls to api.github.com through @tauri-apps/plugin-http.

Checks

npm run typecheck
npm test
cd src-tauri && cargo clippy -- -D warnings && cargo test
npm run tauri build -- --bundles app   # local macOS build

Rules

  • Never print or commit ~/.tauri/pr-radar.key or its password (CI secrets TAURI_SIGNING_PRIVATE_KEY*).
  • site/ (GitHub Pages landing): mock data only (acme), never real private repos.
  • The OAuth client ID in src/lib/auth.ts is public, not a secret.
  • Every feature: local browser demo (skill demo, npm run demo → localhost:1420, mocked data) and explicit user validation before merge/release. Agents commit, push and open the PR as soon as checks are green, without waiting. No merge or release without validation.
  • Branches: work on dev (or a branch → PR to dev). main only accepts PRs from dev; the merge triggers the release.
  • Detailed rules: .claude/rules/ (project, typescript, ui, test, subagents).
  • Skills: worktree (task → PR to dev), mr-review (PR review), grill-me (stress-test a plan), unslop (UI polish, by Damir Sokolovsky, CC BY 4.0).
  • Release: skill release (.claude/skills/release/SKILL.md).
  • Apple notarization: docs/apple-notarization.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.