agentleFS
narenaryannarenaryan/agent-skills/AGENTS.md

agent-skills

AGENTS.md0 starsChanged 39 days agoMITView on GitHub

This repository stores reusable agent skills. When working in this repo, prefer the skill definitions in skills/ as the source of truth for workflow-specific guidance. For any Git-related task in this repository, load and follow the relevant skill under skills/git/ before making changes. When creating or rewriting commit messages for this repository, follow skills/git/conventional-commits/SKILL.md. Current repository convention: ⚡ feat(scope): add example

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Commit message creation or review: skills/git/conventional-commits/SKILL.md

    line 13
  2. Very specific:

    When creating or rewriting commit messages for this repository, follow skills/git/conventional-commits/SKILL.md.

    line 21
  3. Distinctive:

    Use Conventional Commits header syntax.

    line 25
  4. Distinctive:

    Keep the textual type present for tooling compatibility.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md

Purpose

This repository stores reusable agent skills. When working in this repo, prefer the skill definitions in skills/ as the source of truth for workflow-specific guidance.

Git Skill Policy

For any Git-related task in this repository, load and follow the relevant skill under skills/git/ before making changes.

Examples:

  • Commit message creation or review: skills/git/conventional-commits/SKILL.md
  • History rewriting: skills/git/git-rewriting-history/SKILL.md
  • Reset, restore, or undo flows: skills/git/git-reset-mechanics/SKILL.md
  • Merge conflict resolution: skills/git/git-advanced-merging/SKILL.md
  • Lost commit or branch recovery: skills/git/git-data-recovery/SKILL.md

Commit Messages

When creating or rewriting commit messages for this repository, follow skills/git/conventional-commits/SKILL.md.

Current repository convention:

  • Use Conventional Commits header syntax.
  • Prefix the textual type with the mapped emoji from the skill.
  • Keep the textual type present for tooling compatibility.

Example:

⚡ feat(scope): add example

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.