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

repository-orientation

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Establish the repository contract, relevant files, Git state, commands, and constraints before starting unfamiliar work.

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

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
  1. Distinctive:

    Use this skill at the start of substantive work in an unfamiliar checkout.

    line 8
  2. Distinctive:

    Read the root and nearest AGENTS.md files plus the task-relevant README or docs.

    line 10
  3. Distinctive:

    Do not install dependencies, change files, contact external services, or execute unknown scripts merely to orient.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Repository orientation

Use this skill at the start of substantive work in an unfamiliar checkout.

  1. Read the root and nearest AGENTS.md files plus the task-relevant README or docs.
  2. Inspect git status --short --branch, the current branch, worktree, and remotes.
  3. Locate project-owned entry points such as Makefile, task runners, manifests, lockfiles, CI workflows, and relevant tests.
  4. Identify unrelated changes and avoid overlapping them.
  5. State the requested outcome, smallest likely scope, validation plan, and any assumption that could materially change the work.

Do not install dependencies, change files, contact external services, or execute unknown scripts merely to orient. Report environmental blockers separately from repository defects.

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.