agentleFS
Sign inStart free
dbeaverdbeaver/cloudbeaver/.agents/skills/pre-push-checks/SKILL.md

pre-push-checks

Skill5.2k starsChanged 9 days agoApache-2.0View on GitHub

Run ESLint and Prettier before pushing CloudBeaver CE or EE changes, including branch publication and PR pushes.

2 other projects use a version of this.

Trending

Steady talk.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 2 mentionsJun 2026: 1 mentionJul 2026: 5 mentionsAug 2026: 4 mentionsSep 2026: 6 mentionsOct 2026: 4 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the dbeaver/cloudbeaver repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about dbeaver/cloudbeaver

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

See all 50

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

On GitHub · 45

40 more on GitHub

On Hacker News · 3

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. zehuichan/vibe-harness★ 2same name
    2. BrivaHamisi/laravel-shipkit★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Follow repository instructions and use its configured Node/Yarn versions.

    line 12
  2. Distinctive:

    Use the actual PR base, or the repository's development branch unless the user specifies another target.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Pre-push checks

Apply these checks to each repository before a user-authorized push.

1. Prepare

Follow repository instructions and use its configured Node/Yarn versions. Run from the owning webapp/ with installed dependencies and the applicable ESLint/Prettier configurations and ignores. For CE/EE cross-repository changes, use the intended sibling revisions.

2. Select changed files

Use the actual PR base, or the repository's development branch unless the user specifies another target. Resolve missing refs explicitly. Record base and HEAD SHAs; compare the whole branch from their merge base:

git diff --name-only -z --diff-filter=ACMRT <merge-base> HEAD

For working-tree preflight, also include staged, unstaged and untracked non-ignored files. Deduplicate and keep existing regular files; handle nested repositories separately. Use NUL-delimited paths and argument arrays, batching as needed. Explicitly skip empty lists.

3. Run both checks

Pass paths relative to webapp/, respecting each tool's configured scope and ignores:

  • ESLint: yarn lint -- <files>. Keep warnings non-blocking.
  • Prettier: yarn prettier --check --ignore-unknown -- <files>. Include supported non-code files; report ignored/unsupported files as skipped.

ESLint does not run Prettier. Configuration changes may require broader checks under repository rules. Check first; apply --fix / --write only to intended files, review the diff and rerun affected checks. Preserve unrelated changes and resolve failures without suppressing rules or excluding failing files.

4. Verify the pushed snapshot

Validate the committed HEAD being pushed. If the working tree differs, check HEAD in a configured isolated worktree or resolve/report the mismatch. Rerun affected checks after authorized fix commits or changes to HEAD, base, relevant files, configuration or dependencies.

Report checked HEAD/base, commands, file counts/scopes and results. Push only with passing checks for that snapshot; setup errors and unresolved failures block the push. Commit/push authorization must come from the user.

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.

Check your setup, free