Remove all em-dashes from the repo

Every em-dash across docs, skill files, scripts, and JSON/YAML metadata
was rewritten by hand (commas, colons, periods, parentheses, conjunctions)
rather than mechanically substituted, so sentences still read naturally.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Remote Box Agent
2026-08-19 10:03:37 +00:00
co-authored by Claude Sonnet 5
parent e38b908fb7
commit 321658273c
99 changed files with 1155 additions and 1154 deletions
+2 -2
View File
@@ -4,7 +4,7 @@ This project will not add a dedicated verify/check mode (or a separate verify sk
## 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.
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.
@@ -12,4 +12,4 @@ Keeping configuration management to a single skill also avoids the maintenance c
## Prior requests
- #106 Feature request: verify/check mode for setup-matt-pocock-skills
- #106: Feature request: verify/check mode for setup-matt-pocock-skills