agentleFS
mmnto-aimmnto-ai/totem/.claude/skills/prepush/SKILL.md

prepush

Skill18 starsChanged 52 days agoApache-2.0View on GitHub

Pre-push checks — format and lint gates, then the advisory AI review pass

  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. starkware-libs/cairo★ 1.9ksame name
    2. porada/domfiles★ 7same 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 repository13 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Run pnpm run format — fix any formatting issues

    line 8
  2. Very specific:

    Run pnpm exec totem lint — the deterministic enforcement floor (zero LLM).

    line 9
  3. Very specific:

    After all checks pass, proceed with git push.

    line 14
  4. Distinctive:

    If any step fails, fix the issue and re-run from step 1.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Before pushing code:

  1. Run pnpm run format — fix any formatting issues
  2. Run pnpm exec totem lint — the deterministic enforcement floor (zero LLM). Fix any violations before proceeding; the pre-push hook enforces this in every tier.
  3. Run pnpm exec totem review — supplementary AI lanes over the diff (advisory sensors, not a merge gate). Address critical findings; known limits are disclosed in the run output (LLM window truncation on large diffs; non-code files skipped). Note: in strict/agent hook tiers the pre-push hook also runs this command as a push gate — the advisory framing is about what counts as the review of record, not about whether the hook runs it.
  4. Before any external review bot is invited (the operator triggers them; you never do), drive the local lane to settled over the branch-vs-base diff with /review-loop, running totem review --branch (the scope the hook grades; plain totem review reads the working tree whenever it is dirty): WARN and CRITICAL are actionable, INFO is cosmetic, settled is read from the CLI, never derived, and a disputed finding or the max-rounds advisory stops the loop and is reported, as /review-loop says (it also configures review.lanes first; with no lanes there is nothing to settle). When the run names a truncation (the -char review window line, the file listed as "shown in part" and the files listed as "not shown"), the covariate line describes only the delivered slice, whatever settled= says: review the partly shown file and the unseen files over their commit ranges with totem review --diff <range> (a range takes no pathspec, so a slice re-includes every file its commits touch and reads deltas, not the end state), stop and disclose when a single commit or file is itself larger than the window, and quote in the round disposition the whole-branch local-lane: line PLUS the slice runs and what they left unread, never calling the branch diff reviewed while a tail is unread; a lane that ABSTAINS on a truncated diff is a degraded round, never settled. The slicing this step asks you to do by hand is mmnto-ai/totem#3118, which makes the CLI do it. On mmnto-ai/totem#3114 seven of the nine covariate lines quoted through round 7 read settled=false, and four of the seven findings of rounds 5 to 7 sat in files the window had cut.
  5. Before a PR's first push, read the changeset's and the body's guarantees against an inventory of what the code still reads from the checkout (the rule manifest, the config, installed packs, anything not read through the diff's revision), and give every disclosed limit its issue when you file it — a limit that points nowhere is a review round waiting to happen (mmnto-ai/totem#3116 was that round).

After all checks pass, proceed with git push. The review command stamps .reviewed-content-hash automatically on PASS.

If any step fails, fix the issue and re-run from step 1.

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.