Claude projection copies all 50 template skills, including Squad's own repo/release skills, into user projects; Copilot gets 19, so the hosts see different skill sets

Aperta
#2,526 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
66/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, typescript

Direzione di ricerca

Start with projectClaudeSkills in packages/squad-sdk/src/client/adapters/claude-skills.ts and TEMPLATE_MANIFEST in packages/squad-cli/src/cli/core/templates.ts. Compare the projected skills after init --roles --client copilot,claude, including the listed skip rules and any team overrides. Done when both hosts receive the same user-facing template skills, with only the stated host-specific differences.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Version: CLI built from release/prepare-2.0.0-preview.5 @ 38d45d02 (package version 2.0.0-preview.6).

What happens

After a fresh init --client copilot,claude, the two hosts get very different skill sets:

D=$(mktemp -d); cd "$D"; git init -q
node <squad-cli>/dist/cli-entry.js init --roles --client copilot,claude
ls -1 .squad/templates/skills | wc -l   # 50
ls -1 .github/skills | wc -l            # 19
ls -1 .claude/skills | wc -l            # 53 (50 templates − 2 skipped init-mode + 5 squad-coordinator-*)

There are 35 skills only in .claude/skills/. Several of them are about developing and releasing Squad itself and mean nothing in a user's project:

Skill Description (frontmatter)
release-process "Prepare, publish, recover, and verify Squad insider, preview, and stable releases"
versioning-policy "SemVer rules for Squad's stable, preview, insider, and local package versions"
cli-wiring "Checklist for wiring a new Squad CLI command: route it in cli-entry.ts, …"
ci-validation-gates Squad's own CI gates (semver validation, token checks, draft detection)
windows-compatibility Squad's cross-platform path handling
gh-aw-enlistment Enlisting a repo into Squad's gh-aw bootstrap
e2e-template-testing "End-to-end validation of coordinator and agent template changes"
docs-standards Squad-specific documentation patterns

.github/skills/squad-conventions is also Squad-internal ("Core conventions and patterns used in the Squad codebase"), so Copilot projects get one of these too.

Why it matters:

  • Claude Code lists every .claude/skills/* skill to the model and auto-loads them on description match. In a user's repo, "prepare a release" or "bump the version" can pull in Squad's npm release runbook.
  • The same team behaves differently on each host. The Copilot coordinator's skill-aware routing (core protocol item 17) also scans .claude/skills/, so in a dual-host repo the leak reaches Copilot spawns as well.
  • The only workaround today is adding a line to every charter telling members to ignore these skills.

Expected

  • One explicit list of user-facing skills drives every host's projection, the same way TEMPLATE_MANIFEST already drives .github/skills. Template skills that are about the Squad repo itself either aren't shipped in .squad/templates/skills/ or are marked (for example audience: squad-repo in frontmatter) and skipped by every projection.
  • .claude/skills and .github/skills carry the same user-facing template skills. The only differences are deliberate host-specific ones, like the squad-coordinator-* skills and the skipped Copilot Init Mode.

Source

  • packages/squad-sdk/src/client/adapters/claude-skills.ts, projectClaudeSkills, line 74: for (const name of dirs(templatesAbs)) projects every directory under .squad/templates/skills/. It skips only CLAUDE_SKIPPED_TEMPLATE_SKILLS (init-mode, coordinator-init-mode) and team-overridden names.
  • packages/squad-cli/src/cli/core/templates.ts (TEMPLATE_MANIFEST, ../.github/skills/... entries from line ~217): the explicit 19-skill list for .github/skills.

Related: #2438 / #2469 (Claude host), #1436 (drop the template folder from .squad).

🤖 Generated with Claude Code

Lingua principale
TypeScript
Stelle
3.4k
Fork
516
Merge medio
1g 15h
PR unite (30g)
116

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/squad

Tutte le issue di github/squad

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.