Tool suggestion: spec contracts for instruction collections (open source)

Copilot instruction and chatmode files have the same accretion problem as agent skills: nobody can say what each file promises or what done means. We open-sourced skill-spec: a six-section contract template + zero-dependency linter, exit 0/1, CI-ready: github.com/chenhz01/skill-spec. Happy to run a sample across the collection. Ignore if not relevant.

Start by reviewing the linked skill-spec proposal and the repository's instruction and chatmode collection. The issue does not name files, tests, or a specific change; done would first require deciding whether the proposed contract and linter should be adopted and defining the scope.

Written by the indexing model from the issue text.