Add verify/check mode documentation and list-skills script
This commit is contained in:
parent
f71bb975bf
commit
3dae2b1945
2 changed files with 22 additions and 0 deletions
15
.out-of-scope/setup-skill-verify-mode.md
Normal file
15
.out-of-scope/setup-skill-verify-mode.md
Normal file
|
|
@ -0,0 +1,15 @@
|
||||||
|
# Verify/Check Mode for `setup-matt-pocock-skills`
|
||||||
|
|
||||||
|
This project will not add a dedicated verify/check mode (or a separate verify skill) for `setup-matt-pocock-skills`.
|
||||||
|
|
||||||
|
## Why this is out of scope
|
||||||
|
|
||||||
|
A second skill — or a `--verify` flag — for checking whether `docs/agents/*.md` artifacts still match the seed-template schema would duplicate work the existing setup skill already handles in conversation.
|
||||||
|
|
||||||
|
The intended workflow is: **run `/setup-matt-pocock-skills` and tell it to verify your current setup.** The skill is prompt-driven, so the maintainer can scope it to a verification pass ("don't rewrite anything, just check my existing files against the current seed templates and report drift") without needing a separate code path. Adding a flag or a sibling skill would split the surface area of a feature that's already expressible through the natural-language entry point.
|
||||||
|
|
||||||
|
Keeping configuration management to a single skill also avoids the maintenance cost of two skills drifting from each other when seed templates evolve.
|
||||||
|
|
||||||
|
## Prior requests
|
||||||
|
|
||||||
|
- #106 — Feature request: verify/check mode for setup-matt-pocock-skills
|
||||||
7
scripts/list-skills.sh
Executable file
7
scripts/list-skills.sh
Executable file
|
|
@ -0,0 +1,7 @@
|
||||||
|
#!/usr/bin/env bash
|
||||||
|
set -euo pipefail
|
||||||
|
|
||||||
|
REPO="$(cd "$(dirname "$0")/.." && pwd)"
|
||||||
|
|
||||||
|
cd "$REPO"
|
||||||
|
find . -name SKILL.md -not -path '*/node_modules/*' | sed 's|^\./||' | sort
|
||||||
Loading…
Add table
Add a link
Reference in a new issue