agentleFS
pnppnp/powershell/CLAUDE.md

powershell

CLAUDE.md906 starsChanged 2 months agoMITView on GitHub

Repository guidance for this project lives in AGENTS.md — read it first. It is the single source shared by Claude Code, Codex, Copilot and any other agent, so that guidance never drifts between tools. Task procedures live in .agents/skills/. Add new repository guidance to AGENTS.md or a playbook, never to this file — anything written here is invisible to the other tools. Never create an issue. Never create a PR. Never comment, approve, merge, or push unbidden, and never connect…

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

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

  • 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:

    Add new repository guidance to AGENTS.md or a playbook, never to this file — anything written here is invisible to the other tools.

    line 9
  2. Distinctive:

    Never create an issue. Never create a PR: Never comment, approve, merge, or push unbidden, and never connect to a Microsoft 365 tenant on …

    line 14

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

CLAUDE.md

Repository guidance for this project lives in AGENTS.md — read it first. It is the single source shared by Claude Code, Codex, Copilot and any other agent, so that guidance never drifts between tools.

Task procedures live in .agents/skills/.

Add new repository guidance to AGENTS.md or a playbook, never to this file — anything written here is invisible to the other tools.

Read this before touching GitHub

Never create an issue. Never create a PR. Never comment, approve, merge, or push unbidden, and never connect to a Microsoft 365 tenant on your own initiative. gh is authenticated here with repo scope, so all of that is one command away — draft the content, hand over the command, stop. Full rules: Human in the loop.

This is about acting unprompted. When the user asks you directly to connect to a tenant and run something, that is the authorization — do it, confirming each destructive command once. See Running against a tenant.

Claude Code specifics

  • Subagents: .claude/agents/ — permissions-auditor, docs-sync, api-surface-diff, issue-triage, cmdlet-scaffolder. Each one is a thin wrapper delegating to its playbook. The same set exists for Copilot (.github/agents/*.agent.md) and Codex (.codex/agents/*.toml), pointing at the same playbooks — keep the names in step when adding one.
  • Skills: .claude/skills/ — code-review, new-cmdlet. Same arrangement.
  • MCP: .mcp.json configures the GitHub and Microsoft Learn servers. See .agents/README.md.

docs-sync, permissions-auditor and api-surface-diff are read-only and fan out well across the 800+ cmdlets — run them in parallel over separate folders under src/Commands/.

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.