steve/skills
Public Access
1
0
Fork 0
Code Issues 11 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs: restructure skill catalog and standardize setup-skills references

Browse Source 
Reorganize README.md with category sections (engineering, pkm, etc.)
for both user-invoked and model-invoked skills. Add new subcategory
READMEs for skill-authoring and thinking-and-docs. Replace
/setup-matt-pocock-skills references with setup-skills across all SKILLs.
This commit is contained in:
gitadmin
2026-08-27 20:32:28 -04:00
parent 0a4bac7adf
commit a9669c28ec
15 changed files with 183 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/engineering/triage/SKILL.md
+1 -1
View File
@@ -40,7 +40,7 @@ For a PR, the same states read against the attached code: `ready-for-agent` mean
Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`.
These are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run `setup-skills` skill.
State transitions: an unlabeled issue normally goes to `needs-triage` first; from there it moves to `needs-info`, `ready-for-agent`, `ready-for-human`, or `wontfix`. `needs-info` returns to `needs-triage` once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.