agentleFS
kagkarlssonkagkarlsson/db-scheduler/.claude/skills/pre-pr/SKILL.md

pre-pr

Skill1.7k starsChanged 5 days agoApache-2.0View on GitHub

Use before opening a pull request against db-scheduler. Runs /finalize, a fresh-context self-review focused on correctness and readability, a red/green check of the tests, and produces the "Assisted by" line for the PR description.

11 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about kagkarlsson/db-scheduler

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

See all 57

Talked about on GitHub, Stack Overflow and Hacker News (57 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow this before opening a PR, so the maintainer reviews a change that is already in good shape.

    line 8
  2. Very specific:

    Run /finalize (format, license headers, mvn verify).

    line 13
  3. Very specific:

    SQL or JdbcCustomization changes: add a test to CompatibilityTest (under db-scheduler/src/test/java/.../compatibility/) so it runs …

    line 40
  4. Very specific:

    Update README, examples, or UPGRADING.md if behavior or API changed.

    line 45
  5. Distinctive:

    Add a "Verified by:" note only if something beyond the tests was used to verify the change (e.g.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 9 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

Pre-PR self-review

Follow this before opening a PR, so the maintainer reviews a change that is already in good shape. If your tool doesn't support skills, follow the steps manually.

1. Finalize

Run /finalize (format, license headers, mvn verify). Stop and fix if it fails.

2. Self-review in a fresh context

Review the full diff against master using the most capable model available, in a fresh context, not the session that wrote the code. In Claude Code: /code-review high on an Opus-level model.

Review priorities, in order:

  1. Correctness on realistic paths, including multi-node and concurrent execution (optimistic/pessimistic locking, the version guard). This is the core of the library.
  2. Readability and a minimal diff.

Dismiss speculative edge cases unless the fix is trivial and in scope. When a finding can be fixed by removing code instead of adding it, prefer that.

Also check for the patterns AI_POLICY.md warns about: single-use abstractions, duplicated or framework-testing tests, boilerplate, comments that restate the code, and reformatting or renames outside the change.

Fix or consciously dismiss each finding.

3. Verify the tests

  • Red/green: temporarily revert the fix (keep the test) and confirm the new test fails, then restore the fix.
  • SQL or JdbcCustomization changes: add a test to CompatibilityTest (under db-scheduler/src/test/java/.../compatibility/) so it runs against every dialect. Run the affected dialects, e.g. mvn test -Dtest=PostgresqlCompatibilityTest, or all of them with mvn -Ptests-for-ci test.
  • Public API: changes should be additive (new overloads rather than changed signatures).
  • Update README, examples, or UPGRADING.md if behavior or API changed.

4. AI line for the PR description

End the PR description with one line naming the model and tool, e.g.:

Assisted by claude-opus-5-5 (Claude Code).

Add a "Verified by:" note only if something beyond the tests was used to verify the change (e.g. ran it against a real database, manual testing of a Spring Boot app).

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.