agentleFS
Sign inStart free
finosfinos/git-proxy/.github/copilot-instructions.md

git-proxy

Copilot instructions262 starsChanged 2 months agoApache-2.0View on GitHub

Read AGENTS.md for the full project guide. Use the rules below as the highest-priority summary for Copilot surfaces that truncate long instruction files.

  • Commits and pushes

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

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md for the full project guide.

    line 3
  2. Very specific:

    Do not bypass blockForAuth, waiting-authorization checks, or audit logging.

    line 7
  3. Distinctive:

    Keep proxy, service, config, and UI responsibilities separate.

    line 8
  4. Distinctive:

    When changing proxy/processors, test success paths, rejection paths, and audit logging.

    line 14
  5. Very specific:

    Use the standard repo commands: npm run build, npm run test, npm run test:e2e, npm run lint, npm run format:check.

    line 15

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

GitProxy Copilot Instructions

Read AGENTS.md for the full project guide. Use the rules below as the highest-priority summary for Copilot surfaces that truncate long instruction files.

  • Preserve the GitProxy flow: Git HTTP proxy -> ordered action chain -> service API -> audit trail -> approval gate.
  • A push must never reach the real remote unless it is explicitly approved or auto-approved by policy.
  • Do not bypass blockForAuth, waiting-authorization checks, or audit logging.
  • Keep proxy, service, config, and UI responsibilities separate. Do not place policy logic ad hoc in request handlers.
  • The action chain is the core abstraction. Put reusable enforcement logic in processors, organization-specific logic in plugins, and UI/auth state changes in the service layer.
  • Processor order matters. If logic depends on cloned repositories, diffs, or earlier artifacts, place it accordingly.
  • Processors must be idempotent, use the Action object instead of shared mutable state, and preserve audit traceability.
  • Configuration changes must update schema validation, keep backward-compatible defaults, and avoid weakening security by default.
  • Authentication strategies apply to UI and approval workflows. Git push identity is derived from commit metadata, not interactive auth.
  • When changing proxy/processors, test success paths, rejection paths, and audit logging. When changing config, test invalid values and defaults.
  • Use the standard repo commands: npm run build, npm run test, npm run test:e2e, npm run lint, npm run format:check.

Download now (ZIP)

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 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 repository10 other files it gives its agents.

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