Defame1297
ed8c99efbd
The #113 sweep rested on CLAUDE.md's premise that rtk either filters or passes through unchanged, so prefixing is always safe. Measured against rtk 0.42.4, that premise is false for several of the commands the sweep prefixed, and two skills were left giving wrong answers silently. Why: - `rtk git worktree list --porcelain -z` discards both flags and renders its own format. The `locked`/`lock_reason` fields git-worktrees Step 2 must emit are absent entirely, and paths under $HOME are abbreviated to `~/`. - `rtk git branch --list <name>` prints a phantom `* ` line even when nothing matches, so git-branches' stated ambiguity test — "output from both means the name is ambiguous" — reported every name as ambiguous. `tag --list` is a clean passthrough, so only one half broke. - `rtk git diff --name-only`/`--name-status` append a `Changes:` trailer to output documented as "one per line"; `--word-diff` emits none of the `[-removed-] {+added+}` markers its table describes; `rtk git log -L` truncates each line at ~72 chars, on the one command whose purpose is showing line content. - `rtk git stash pop` prints only `FAILED: git stash pop`, swallowing the conflict diagnostic and retained-entry message the surrounding prose tells the agent to rely on. Implementation notes: - Eleven sites reverted to bare `git`, each carrying its reason inline so the next sweep does not undo it. `mergetool` and `rebase -i` are reverted on clause 3's interactive limb only: the TTY defect does not reproduce — rtk filters exactly twelve subcommands and execs the rest — and ADR-0023 records that measurement rather than a convenient one. - ADR-0023 states the rule repo-wide with a third clause: a command whose output the skill parses, or which is interactive, stays bare. `plugins/git/README.md` is reduced to a pointer; its claim that gitea skills "contain no git/rtk mentions at all" was false, and its citation of `hard-rules.md` pointed at a file containing no occurrence of "rtk". - Eight gitea sites swept, all verified byte-identical passthroughs first. - `scripts/check-rtk-prefix.sh` gates clause 1. Run against main's pre-sweep corpus it reports 99 findings including every gitea site, so it would have caught the drift #113 was filed about. Impact: the gate covers clause 1 only, in shell-tagged fences and the opening span of Run cells. Clause 2 is not gateable — "Run `git switch`" and "`git switch` refuses" are the same tokens — and prose bullets are invisible to it. Both limits are recorded in gates.md rather than left implied. Refs: #113 ADR: 0023 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP
gitea-issues
Read and write Gitea issues — list, get, create, comment, close, and search — via the Gitea MCP server.
What it does
This skill handles the issue lifecycle (list_issues, issue_read, issue_write, search_issues):
listing repo issues, reading a single issue's details/comments/labels, creating an issue, updating
its state, adding/editing comments, applying labels, and searching issues/PRs across repositories.
The create flow closes out four enrichments deferred from issue #6 comment #848: label inference
and milestone assignment (both by composing gitea-labels-milestones), an assignee workaround for
the blocked get_me scope, and the "Depends on #N" dependency-linking convention. It supersedes the
issue/issue <N>/issue close <N>/issue comment <N> dispatch this plugin's old single flat
Gitea skill carried, retired when the plugin was split into per-domain deep modules.
Before you start
Requires a Gitea MCP server configured with a token holding write:issue + write:repository.
Requires a git remote named origin pointing at the Gitea instance, unless an orchestrating caller
(e.g. gitea-workflow) already resolved owner/repo for you.
How it composes
This skill composes gitea-labels-milestones for all label inference, label-name-to-ID
resolution, and milestone lookup, rather than duplicating that taxonomy or its resolution logic —
see references/enrichments.md for the call protocol. Managing the label and milestone definitions
themselves (create/edit/delete a label, create/close a milestone) is out of scope here and goes to
gitea-labels-milestones directly.
One boundary the description does not spend characters on, because it was never going to win an
issue request: local git branch or commit work belongs to gitea-branches (Gitea-side) or
git-branches (working copy).
Usage
/gitea-issues
Describe your task: list issues, create one, get/comment/close/label a specific issue number, or
search across repos. See SKILL.md's dispatch table for the full set of recognized invocations.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents — dispatch table, Gotchas |
references/issues.md |
Verified call signatures and mechanics for list_issues/issue_read/issue_write |
references/search.md |
Verified call signature and mechanics for search_issues |
references/enrichments.md |
Create-flow enrichments — label inference, milestone assignment, assignee workaround, dependency-linking convention |
references/sources.md |
Research sources backing the issue guidance |