agentleFS
Sign inStart free
EvanBattenEvanBatten/pstack-for-cc/CLAUDE.md

pstack-for-cc

CLAUDE.md2 starsChanged 46 days agoMITView on GitHub

The Claude Code port of pstack. ~/.claude/skills links into a clone of this repo, so a change to a skill is live on the next read. Start with README.md.

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never rewrite the three tags or the commits under them.

    line 7
  2. Very specific:

    Keep disable-model-invocation when you add a skill, or its description loads into every session.

    line 10

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

pstack-for-cc

The Claude Code port of pstack. ~/.claude/skills links into a clone of this repo, so a change to a skill is live on the next read. Start with README.md.

Rules

  • Never rewrite the three tags or the commits under them. They are the baseline every diff starts from.
  • Record every change in scripts/drift.mjs. Commit the change, run node scripts/drift.mjs, and commit DRIFT.md. CI fails when a changed file has no class.
  • install.json decides what a machine installs. Add a new skill or agent to it, or it stays in the repo and never reaches ~/.claude.
  • Keep disable-model-invocation when you add a skill, or its description loads into every session.
  • Prove a change to a skill, the hook or a script with the verify-pstack skill before you call it done.
  • Git Bash rewrites an argument that starts with / into a Windows path, so claude -p "/bro" sends C:/Program Files/Git/bro. Pipe the prompt on stdin instead, as in printf '%s' "/bro" | claude -p. Do not start a session with MSYS_NO_PATHCONV=1. A hook that passes a ~ path to Node then fails, and the session loses the pstack context.
  • Edit JavaScript that contains regexes or escapes with the Edit or Write tool. A Python or shell heredoc eats the backslashes.
  • The notes in docs/research/ follow the rules in docs/research/README.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