fix(skills): collapse verb-enumerated descriptions to one capability clause
An independent audit of the ADR-0020 retrofit (issue #99) found that git-submodules, git-worktrees, and gitea-files each collapsed their description length correctly during retrofit but left the capability clause as a verb enumeration (e.g. "Create, list, lock, move, remove, prune, or repair") instead of ADR-0020's required single clause. The deterministic char-count gate can't catch this — it's a qualitative rubric violation the retrofit commits' own messages never claimed to address, only measurable length/word-count fixes. Validated clean via skill-audit and skill-size-check after the fix; boundary clauses and routing targets left untouched. Refs #99
This commit is contained in:
@@ -2,9 +2,9 @@
|
||||
name: gitea-files
|
||||
|
||||
description: >
|
||||
Use when reading or writing files in a Gitea repository rather than on the local filesystem —
|
||||
read, list, walk the tree, create, update, or delete — even when the user does not say "Gitea".
|
||||
Not commit history -> `gitea-branches`. Not pull requests -> `gitea-prs`.
|
||||
Use when reading or writing files or directories in a Gitea repository via the MCP server,
|
||||
rather than the local filesystem — even when the user does not say "Gitea". Not commit
|
||||
history -> `gitea-branches`. Not pull requests -> `gitea-prs`.
|
||||
|
||||
compatibility: Requires the Gitea MCP server configured with a token scoped to at least
|
||||
write:repository. Tested with a token holding write:issue + write:repository; write:issue
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
name: gitea-files
|
||||
|
||||
description: >
|
||||
Use when reading or writing files in a Gitea repository rather than on the local filesystem —
|
||||
read, list, walk the tree, create, update, or delete — even when the user does not say "Gitea".
|
||||
Not commit history -> `gitea-branches`. Not pull requests -> `gitea-prs`.
|
||||
Use when reading or writing files or directories in a Gitea repository via the MCP server,
|
||||
rather than the local filesystem — even when the user does not say "Gitea". Not commit
|
||||
history -> `gitea-branches`. Not pull requests -> `gitea-prs`.
|
||||
|
||||
compatibility: Requires the Gitea MCP server configured with a token scoped to at least
|
||||
write:repository. Tested with a token holding write:issue + write:repository; write:issue
|
||||
|
||||
Reference in New Issue
Block a user