agentleFS
Sign inStart free
vosslabvosslab/vosslab-skills/skills/orientation/repo-rules-reader/SKILL.md

repo-rules-reader

Skill5 starsChanged 22 days agoMITView on GitHub

Orient to repository rules for an explicit orientation request, a workflow that requires a rules receipt, or substantial repository work when no valid same-session receipt exists.

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these required paths:

    line 14
  2. Very specific:

    When pytest work or its policy materially affects the request, state what docs/PYTEST_STYLE.md considers a fragile pytest.

    line 23
  3. Very specific:

    When it materially affects the request's scope or a decision, state the relevant most recent change from docs/CHANGELOG.md.

    line 25

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

Read repo rules

Purpose

Establish one authoritative rules receipt for the current repository work session.

Workflow

  1. Read these required paths:
    • AGENTS.md
    • docs/*_STYLE.md
    • the latest dated entry in docs/CHANGELOG.md
  2. Retain and apply the rules throughout subsequent work. Treat the receipt as valid for the same session while the task scope and relevant guidance remain unchanged.
  3. Give a concise read receipt:
    • Name the files read.
    • From AGENTS.md, include source source_me.sh && python3 when specified.
    • When pytest work or its policy materially affects the request, state what docs/PYTEST_STYLE.md considers a fragile pytest.
    • When it materially affects the request's scope or a decision, state the relevant most recent change from docs/CHANGELOG.md.
  4. Answer any exact questions or requested format from the file content.
  5. Continue the task with the rules applied, or be ready for a task to be provided. Reuse the receipt without rereading when another workflow requests orientation in the same unchanged scope; reread when the scope changes or relevant guidance may have changed.

Claude Code also reads docs/CLAUDE_HOOK_USAGE_GUIDE.md.

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