transcripts-mcp / rules
Cursor rule8 starsChanged 2 months agoMITView on GitHub
Calldiff: optionally include a call-stack diff in plans, design docs, and PR descriptions when call flow actually changed and a tree would help
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .deepsec/AGENTS.mdAGENTS.md
- .cursor/rules/010-workflow.mdcCursor rule
- .cursor/rules/020-codebase-structure.mdcCursor rule
- .cursor/rules/030-coding-style.mdcCursor rule
- .cursor/rules/031-never-use-any.mdcCursor rule
- .cursor/rules/032-import-rules.mdcCursor rule
- .cursor/rules/050-testing.mdcCursor rule
- .cursor/rules/070-comments-defensive-programming.mdcCursor rule
- .cursor/rules/080-ai-interaction.mdcCursor rule
- .cursor/rules/090-changesets.mdcCursor rule
- .cursor/rules/990-cursor-rule-editing-workaround.mdcCursor rule
- .cursor/rules/999-mdc-format.mdcCursor rule
- adversarial-reviewSkill
- agent-browserSkill
- calldiffSkill
- changesetSkill
- commitSkill
- deslopSkill
- fix-prSkill
- git-conventionsSkill
- humanizerSkill
- improve-codebase-architectureSkill
- logging-best-practicesSkill
- opensrcSkill
- rebaseSkill
- recomposing-commitsSkill
- security-reviewSkill
- show-meSkill
- simplifySkill
- thermo-nuclear-code-quality-reviewSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
We split this 095-calldiff.mdc 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
- Very specific: line 29
Use npx calldiff@latest. Defaults compare HEAD vs the working tree.
- Distinctive: line 51
If you chose to run calldiff and it produces nothing useful, fall back to a short hand-written call tree per the show-me skill, or omit the …
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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.
Files
--- description: Calldiff: optionally include a call-stack diff in plans, design docs, and PR descriptions when call flow actually changed and a tree would help alwaysApply: true --- # Call-stack diffs with calldiff Calldiff is optional. Use it only when a call-stack tree would help a reviewer understand a real call-flow change. Do **not** include it in routine chat summaries, status updates, or wrap-ups. ## When to use Include a call-stack diff in a plan, design doc, or PR description when **all** of these are true: - The change rewires call flow: new, removed, or moved callees; refactored control flow; extracted or inlined functions - The new vs old call tree is not obvious from the code or a short prose description - The audience is a reviewer who needs to see how control flow moved ## When to skip Skip calldiff (do not run it, do not paste a tree, do not mention that you skipped it) when: - The message is a normal chat reply, task wrap-up, or end-of-turn summary - The change is UI/copy, styling, config, dependency, translation, tests, or docs - The call-flow change is small or obvious (renames, extra args, a single new call) - calldiff would produce noise, an empty tree, or no useful signal ## How to run Use `npx calldiff@latest`. Defaults compare HEAD vs the working tree. ```bash npx calldiff@latest diff --file packages/adapters/src/cursor.ts npx calldiff@latest diff main --entry toMessage ``` Other useful commands: ```bash npx calldiff@latest tree --entry toMessage npx calldiff@latest reach --entry grepTranscripts --to toMessage ``` Scope with `--file` / `--entry` and `--maxDepth`. Keep the pasted tree to the entrypoints that changed. Paste the output in a fenced `diff` block. ## Caveats - Calldiff is syntactic (tree-sitter). Dynamic calls and trait-object dispatch will not resolve. - Grammars download on first use into `~/.cache/calldiff/grammars`. - If you chose to run calldiff and it produces nothing useful, fall back to a short hand-written call tree per the [show-me](../../.agents/skills/show-me/SKILL.md) skill, or omit the tree entirely.
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
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.