agentleFS
sodejmsodejm/portable-agent-repository-kit/.claude/skills/gitignore-audit/SKILL.md

gitignore-audit

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Inspect a repository and recommend narrow evidence-backed ignore patterns without modifying files or hiding tracked artifacts.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Read all applicable ignore files and git status --ignored --short.

    line 10
  2. Distinctive:

    Check whether each candidate is already tracked or intentionally committed.

    line 13
  3. Distinctive:

    Prefer the narrowest stable pattern.

    line 14
  4. Distinctive:

    Never display secret values and never use ignore rules as remediation for a secret that is already committed.

    line 19

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

Gitignore audit

This workflow is read-only unless a later request explicitly asks for edits.

  1. Read all applicable ignore files and git status --ignored --short.
  2. Identify untracked generated output, caches, local settings, credentials, editor state, or platform files using file contents and project tooling as evidence.
  3. Check whether each candidate is already tracked or intentionally committed.
  4. Prefer the narrowest stable pattern; avoid broad extension or directory rules that could hide source, fixtures, documentation, lockfiles, or migrations.
  5. Report candidates grouped as high confidence, project decision, and do not ignore. Include the evidence and risk for each.

Never display secret values and never use ignore rules as remediation for a secret that is already committed.

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.