agentleFS
Sign inStart free
KletoWorksKletoWorks/complex-md/.github/copilot-instructions.md

complex-md

Copilot instructions1 starsChanged 17 days agoMITView on GitHub

COMPLEX.md at the repository root maps where edits here are risky. It is computed from the import graph and the commit history. When you review a pull request: 1. For each changed file that COMPLEX.md lists under hotspots or load_bearing, check that the change did what that file's paragraph in "Why these files are hot" asks. Most paragraphs name a test command. 2. For each changed file in a co_change pair, check whether the partner also needed a change. If…

The file

We split this copilot-instructions.md into the rules it gives an agent

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you review a pull request:

    line 6
  2. Very specific:

    When CLI behavior changes, check that cli/test/truth.test.js still passes.

    line 16
  3. Very specific:

    When editing one file of a co_change pair, or a file in one side of a seams pair, open the partner and state in your change description …

    line 36
  4. Very specific:

    After refactoring a listed hotspot, regenerate the map: npx complex-md, or run the complex-md skill.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md

Instructions for Copilot in this repository

COMPLEX.md at the repository root maps where edits here are risky. It is computed from the import graph and the commit history.

When you review a pull request:

  1. For each changed file that COMPLEX.md lists under hotspots or load_bearing, check that the change did what that file's paragraph in "Why these files are hot" asks. Most paragraphs name a test command.
  2. For each changed file in a co_change pair, check whether the partner also needed a change. If the partner is unchanged, say so in a comment and name the partner.
  3. Name the covering tests from COMPLEX.md that the change should run. The gate is the exit code of cd cli && npm test.
  4. When CLI behavior changes, check that cli/test/truth.test.js still passes. It fails on a public sentence that the code contradicts.

Rules from AGENTS.md: add no runtime dependency, add no network call outside the model calls in cli/src/generate.js, and do not edit COMPLEX.md, .claude/rules/ or .github/instructions/complex-md/ by hand, because they are generated.

<!-- BEGIN complex-md (spec 0.3) -->

COMPLEX.md: the structural risk map

COMPLEX.md at the repository root is a computed map of where edits are risky and where bugs get fixed, built from the dependency graph and the commit history. Its hotspots, load_bearing, co_change and seams lists name specific files and areas. When your work touches one of them:

  1. IMPORTANT: before editing a file listed under hotspots or load_bearing, read its paragraph in COMPLEX.md under "Why these files are hot" and do what that paragraph's last sentence says before you change the file.
  2. When editing one file of a co_change pair, or a file in one side of a seams pair, open the partner and state in your change description whether the partner also needed a change.
  3. Fixing a bug whose location you do not yet know, check the hotspots rows with the highest fixes count before searching the whole repository; past fixes predict where the next one lands.
  4. Entering this repository cold, read the files under "What to read first" in order before your first edit.

After refactoring a listed hotspot, regenerate the map: npx complex-md, or run the complex-md skill.

<!-- END complex-md (spec 0.3) -->

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