Add SKILL.md and copilot-instructions.md for core CAPs#1895
Add SKILL.md and copilot-instructions.md for core CAPs#1895anupsdf merged 2 commits intostellar:masterfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds contributor/assistant guidance files to help keep Core Advancement Proposal (CAP) edits consistent and reviewable across the repository.
Changes:
- Add
.github/copilot-instructions.mdwith repository-wide editing guidance focused on CAP work undercore/. - Add
.claude/skills/core/SKILL.mddefining a “core” skill/workflow for drafting/editing CAPs and synchronizing CAP status withcore/README.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/copilot-instructions.md | Establishes CAP-focused editing and scope-discipline rules plus formatting guidance (incl. ./bin/prettier.sh). |
| .claude/skills/core/SKILL.md | Introduces a structured workflow for CAP authoring and CAP status synchronization against core/README.md. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
dmkozh
left a comment
dmkozh
left a comment
There was a problem hiding this comment.
Do we have any evidence/motivation to consider this skill useful? It seems quite trivial to me, I'd expect any agent to be able to easily do mass edits on CAPs without messing up.
Most likely any agent would be able to do edits to move the CAPs to different section when status changes. However, I added this to make the instructions be more specific to minimize AI messing things up (like in case there is a regression in a new AI model). |
dmkozh
left a comment
dmkozh
left a comment
There was a problem hiding this comment.
Ok, I guess we could try this out, but I'm generally really skeptical of pre-emptively adding skills or copilot instructions without solving a specific issue.
Yeah, I think this is not that important but something we could try out. I have seen formatting issues before and even I have forgotten to keep the README and individual CAPs in sync, so I thought we could leverage AI with specific instructions. |
+1 plus, we should be experimenting with skills locally with ai tooling, because iterating is important, and then pushing to repos when we find something that works. Is this a skill we have used or is this written but never used? |
Oh. I have actually tested the SKILL before pushing. I used it for generating the changes in #1894 and then separated the SKILL.md and copilot-instructions.md into a separate GH branch so I could have a separate PR. So, its not untested. Sorry if I didn't clarify that earlier. cc. @dmkozh , @leighmcculloch |
|
Thanks for clarifying! Apologies for incorrectly reading between the lines. |
Add SKILL.md and copilot-instructions.md for core CAPs.