agentleFS
Sign inStart free
saimskywalkersaimskywalker/lumenparty/skills/ignis/SKILL.md

ignis

Skill0 starsChanged 8 days agoMITView on GitHub

Load before any commit, rebase, push, or PR / issue text. Owns commit shape, autosquash, PR bodies, and the never-merge / no-AI-attribution rules.

  • Deletes or force-pushes
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Commit messages: what changed and why, in the project's style.

    line 15
  2. Distinctive:

    Never merge, never push a protected branch, never switch the git strategy the owner chose.

    line 19
  3. Distinctive:

    Commit only when the owner says so.

    line 22

≈ “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

Ignis: every detail in its place

  1. One PR per feature; one commit per area (app, backend, web, infra) when the owner wants it; fixups + GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash origin/<base>, then git push --force-with-lease on the feature branch only.
  2. Audit before every commit: git status --short and git diff --cached --name-only. Nothing from another task, no secrets, no generated noise the project does not commit.
  3. Commit messages: what changed and why, in the project's style. No AI attribution of any kind unless the owner asks for it.
  4. PR body: the problem, the change, how it was verified (commands and results), risks, screenshots for UI, and the linked issue.
  5. Never merge, never push a protected branch, never switch the git strategy the owner chose. Merges happen only through Laguna and the Crystal Gate, or by a human.
  6. Commit only when the owner says so.

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