refactor(skills): retrofit the corpus to the ADR-0020 context contract #129
@@ -2,8 +2,8 @@
|
||||
name: git-submodules
|
||||
|
||||
description: >
|
||||
Use when managing Git submodules — adding, updating, pinning, inspecting,
|
||||
repointing, or removing a nested repository inside a superproject.
|
||||
Use when managing Git submodules — the full lifecycle of a nested
|
||||
repository inside a superproject.
|
||||
Not multiple checkouts of one repo -> `git-worktrees`.
|
||||
Not the superproject's own remotes -> `git-remotes`.
|
||||
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: git-worktrees
|
||||
|
||||
description: >
|
||||
Use when working on several branches at once without stashing.
|
||||
Create, list, lock, move, remove, prune, or repair git worktrees.
|
||||
Use when working on several branches at once without stashing —
|
||||
manages the full lifecycle of a git worktree.
|
||||
Not ordinary branch switching or checkout -> `git-branches`.
|
||||
Not interactive multi-step git guidance -> `git-workflow`.
|
||||
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: git-submodules
|
||||
|
||||
description: >
|
||||
Use when managing Git submodules — adding, updating, pinning, inspecting,
|
||||
repointing, or removing a nested repository inside a superproject.
|
||||
Use when managing Git submodules — the full lifecycle of a nested
|
||||
repository inside a superproject.
|
||||
Not multiple checkouts of one repo -> `git-worktrees`.
|
||||
Not the superproject's own remotes -> `git-remotes`.
|
||||
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: git-worktrees
|
||||
|
||||
description: >
|
||||
Use when working on several branches at once without stashing.
|
||||
Create, list, lock, move, remove, prune, or repair git worktrees.
|
||||
Use when working on several branches at once without stashing —
|
||||
manages the full lifecycle of a git worktree.
|
||||
Not ordinary branch switching or checkout -> `git-branches`.
|
||||
Not interactive multi-step git guidance -> `git-workflow`.
|
||||
|
||||
|
||||
@@ -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