agentleFS
aveprojectaveproject/ave/.claude/skills/git-guardrails/SKILL.md

git-guardrails

Skill24 starsChanged 14 days agoApache-2.0View on GitHub

Block: push --force, reset --hard, clean -fd, rebase -i on pushed commits. Before commit: python scripts/validate_records.py # all records valid pytest tests/ -x -q # rules fire correctly NEVER renumber an ave_id. Once AVE-2026-00001 is published, that number is permanent. A wrong record gets deprecated, not renumbered.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use triage and code-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER renumber an ave_id. Once AVE-2026-00001 is published, that number is permanent.

    line 11

“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

git-guardrails — ave

Block: push --force, reset --hard, clean -fd, rebase -i on pushed commits.

Before commit: python scripts/validate_records.py # all records valid pytest tests/ -x -q # rules fire correctly

Record-specific

NEVER renumber an ave_id. Once AVE-2026-00001 is published, that number is permanent. A wrong record gets deprecated, not renumbered.

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.