agentleFS
clideyclidey/whodb/.agents/skills/review-checklist/SKILL.md

review-checklist

Skill5.1k starsChanged 3 days agoApache-2.0View on GitHub

Pre-commit/pre-PR review checklist for verifying changes are complete and correct

8 other projects use a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 8 mentionsApr 2026: 4 mentionsMay 2026: 5 mentionsJun 2026: 6 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 9 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the clidey/whodb repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about clidey/whodb

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 7

    Distinctive

    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:

    Run this checklist before marking work complete or creating a PR.

    line 8
  2. Distinctive:

    All new exports are imported somewhere and all new functions and types are used (search for their names)

    line 32
  3. Distinctive:

    No commented-out code, and no code left over from an abandoned approach

    line 34
  4. Distinctive:

    No sensitive data logged (passwords, tokens, connection strings)

    line 37
  5. Very specific:

    All user-facing strings use t('key')

    line 41
  6. Distinctive:

    No hardcoded English text

    line 42
  7. Distinctive:

    No CE code that depends on or names another edition

    line 56
  8. Distinctive:

    No build binaries left behind

    line 62
  9. Distinctive:

    No TODO comments (unless tracking a known issue)

    line 63

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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
SKILL.md

Review Checklist

Run this checklist before marking work complete or creating a PR. The agent Stop hooks already build core/ and cli/, typecheck the frontend, check that literal t('key') calls have an en_US entry, and run the agent-doc checker for changed areas. Lint (which covers SQL fmt.Sprintf, database-type constants in shared code and interface{}), the frontend production build and tests still need running.

1. Lint

# Backend (if core/ Go files changed)
cd core && ./lint.sh

# CLI (if cli/ Go files changed)
cd cli && make lint

# Frontend (if TS/TSX files changed)
cd frontend && pnpm lint

2. Frontend Production Build

cd frontend && pnpm run build:ce   # if TS/TSX files changed

3. Dead Code

  • All new exports are imported somewhere and all new functions and types are used (search for their names)
  • Removed code doesn't leave orphaned imports, variables or helpers
  • No commented-out code, and no code left over from an abandoned approach

4. Security

  • No sensitive data logged (passwords, tokens, connection strings)
  • No hardcoded credentials

5. Localization (if UI changed)

  • All user-facing strings use t('key')
  • No hardcoded English text
  • New or updated translation keys are limited to en_US unless the user explicitly asked for other languages

6. Testing

  • data-testid attributes preserved on refactored elements
  • New UI features have corresponding E2E test coverage
  • Run relevant tests:
    cd core && go test ./...                          # or: bash dev/run-backend-tests.sh all
    bash dev/run-cli-tests.sh                         # if cli/ changed
    cd frontend && pnpm e2e:db:headless <affected-database>

7. Architecture

  • No CE code that depends on or names another edition
  • GraphQL uses source-first types (not Database*)
  • Plugin changes go through PluginFunctions interface
  • Exported Go and TypeScript symbols have doc comments (no linter checks this)

8. Cleanup

  • No build binaries left behind
  • No TODO comments (unless tracking a known issue)
  • Diff is minimal — only lines required by the request

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.