kubefleet-devkubefleet-dev/kubefleet/.squad/copilot-instructions.md

kubefleet

Copilot instructions164 starsChanged 6 days agoApache-2.0View on GitHub

You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously, follow these guidelines. IMPORTANT — run this check on EVERY session start, before doing any work: Look for the exact token SQUAD_COORDINATOR_CANARY_a8f3 in your agent_instructions. This token is placed at the end of squad.agent.md. If it is missing, the coordinator file is missing or truncated. When the token is missing, you MUST: 1. STOP — do not proceed with standard Squad behavior.…

1 other project uses a version of this.

Adopted by

Most recently taken up by

microsoft/github-vteam-industry-demosword for word, first seen Oct 25, 2026

Other versions1 project uses a version of this.
Word for word · 1
microsoft/github-vteam-industry-demos★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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,349 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 repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-collaborationSkill
- coordinator-init-modeSkill
- coordinator-response-modeSkill
- coordinator-source-of-truthSkill
- cross-squad-communicationSkill
- cross-squadSkill
- error-recoverySkill
- git-workflowSkill
- iterative-retrievalSkill
- reflectSkill
- reviewer-protocolSkill
- secret-handlingSkill
- session-recoverySkill
- squad-conventionsSkill
- squad-helpSkill
- squadSkill
- squad-version-checkSkill
- test-disciplineSkill
- tiered-memorySkill
- {skill-name}Skill

The file

Show its rules and text

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

13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Look for the exact token SQUAD_COORDINATOR_CANARY_a8f3 in your agent_instructions.
line 9
Distinctive:
Do not continue with normal Squad routing, spawning, PR, or branch-protection behavior after emitting the warning.
line 17
Distinctive:
Before starting work on any issue:
line 21
Very specific:
Read .squad/team.md for the team roster, member roles, and your capability profile.
line 23
Very specific:
Read .squad/routing.md for work routing rules.
line 24
Very specific:
If the issue has a squad:{member} label, read that member's charter at .squad/agents/{member}/charter.md to understand their domain …
line 25
Very specific:
Before starting work, check your capability profile in .squad/team.md under the Coding Agent → Capabilities section.
line 29
Distinctive:
Use the squad branch convention:
line 40
Distinctive:
When opening a PR:
line 48
Very specific:
If the issue had a squad:{member} label, mention the member: Working as {member} ({role})
line 50
Very specific:
If this is a 🟡 needs-review task, add to the PR description: ⚠️ This task was flagged as "needs review" — please have a squad member …
line 51
Very specific:
Follow any project conventions in .squad/decisions.md
line 52
Distinctive:
If you make a decision that affects other team members, write it to:
line 56

≈ “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

Copilot Coding Agent — Squad Instructions

You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously, follow these guidelines.

Coordinator Canary Check

IMPORTANT — run this check on EVERY session start, before doing any work:

Look for the exact token SQUAD_COORDINATOR_CANARY_a8f3 in your agent_instructions. This token is placed at the end of squad.agent.md. If it is missing, the coordinator file is missing or truncated.

When the token is missing, you MUST:

STOP — do not proceed with standard Squad behavior.

WARN the user with this exact message:

⚠️ Squad coordinator (squad.agent.md) appears to be missing or truncated. The canary token was not found. Do NOT proceed with standard Squad behavior — Squad's safety rails are not loaded. Please restart your session.

Do not continue with normal Squad routing, spawning, PR, or branch-protection behavior after emitting the warning.

Team Context

Before starting work on any issue:

Read .squad/team.md for the team roster, member roles, and your capability profile.
Read .squad/routing.md for work routing rules.
If the issue has a squad:{member} label, read that member's charter at .squad/agents/{member}/charter.md to understand their domain expertise and coding style — work in their voice.

Capability Self-Check

Before starting work, check your capability profile in .squad/team.md under the Coding Agent → Capabilities section.

🟢 Good fit — proceed autonomously.
🟡 Needs review — proceed, but note in the PR description that a squad member should review.

🔴 Not suitable — do NOT start work. Instead, comment on the issue:

🤖 This issue doesn't match my capability profile (reason: {why}). Suggesting reassignment to a squad member.

Branch Naming

Use the squad branch convention:

squad/{issue-number}-{kebab-case-slug}

Example: squad/42-fix-login-validation

PR Guidelines

When opening a PR:

Reference the issue: Closes #{issue-number}
If the issue had a squad:{member} label, mention the member: Working as {member} ({role})
If this is a 🟡 needs-review task, add to the PR description: ⚠️ This task was flagged as "needs review" — please have a squad member review before merging.
Follow any project conventions in .squad/decisions.md

Decisions

If you make a decision that affects other team members, write it to:

.squad/decisions/inbox/copilot-{brief-slug}.md

The Scribe will merge it into the shared decisions file.

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