Files

Defame1297 37382cb72a refactor(gitea-labels-milestones): retrofit to the ADR-0020 context contract

Description 835 -> 214 chars, body 669 -> 426 words, Gotchas 8 entries/63% of
body -> 3/20.4%. Clears the description FAIL, all three Vale CompositionNote
errors and both Gotchas suggestions. 63% was the worst Gotchas ratio in the
corpus.

Cut the composition sentence to README -- it changes no routing decision and an
agent picks this skill because the user asked about labels, not because two
other skills call it. Cut the capability enumeration; 'list, create, edit,
delete' decompose 'reading or writing' and add no trigger.

Boundary clauses are now one arrow per target. The resolver extracts only the
first name per arrow clause, so the previous '-> gitea-issues / gitea-prs' left
gitea-prs neither dangling nor checked while validate.sh reported 1 of 1. Now
2 of 2.

Makes org-scoped label resolution executable. The org label pool was reachable
in principle -- four *_org_label* methods, and a claim to own name-to-ID
resolution -- but list_org_labels takes org, and Step 1 derived only owner and
repo, so both resolution procedures stalled at the fallback. Fixed once at the
identity step rather than per-procedure. get_user_orgs is outside allowed-tools,
so the failing call is the discriminator: a failure means the owner is a user
account with no org pool, which is an answer, not an error.

Corrects a Gotcha that was false for create_repo_label/create_org_label and
collided with the literal tool name label_write. Same false claim removed from
README.

Refs #99

2026-08-30 12:29:18 +00:00

3.8 KiB

Raw Blame History

topic, source_keys

topic

source_keys

label-inference

context7-websites-gitea

gitea-mcp-repo

Label inference guide

Maps context-pattern signals from conversation content (an issue being drafted, a bug report, a PR description) to this repo's Kind/* / Priority/* / Status/* label taxonomy. Used by gitea-issues and gitea-prs before creating or updating an issue/PR, and directly when the user asks to label something without naming exact labels.

Scoped labels are mutually exclusive — replace, don't stack

Each of Kind/*, Priority/*, Status/* is treated as a scoped-label group by convention (the / delimiter naming pattern). Gitea's exclusive flag — the mechanism that would let the server itself enforce one-label-per-scope — is documented as an org-labels-only setting, and the repo-level label_write methods used here don't accept it at all. So exclusivity within these scopes is a convention this skill enforces client-side, not something the server guarantees: applying a new label within a scope is expected to replace any existing label in that same scope on the target issue/PR, not add alongside it. When inference selects a Priority/High label and the issue already carries Priority/Medium, the write should result in only Priority/High remaining — use replace_labels scoped to that group's labels, or at minimum remove the superseded label before adding the new one. Never leave two labels from the same scope applied at once.

Signal → label mapping

Kind/* (what kind of work this is):

Signal in context	Label
Bug report, error, crash, unexpected behavior, "broken", "doesn't work"	`Kind/Bug`
New capability, "add support for", net-new functionality	`Kind/Feature`
Improvement to existing behavior, "make X better", refactor with behavior change	`Kind/Enhancement`
Docs-only change, README/comment/guide updates	`Kind/Documentation`
Vulnerability, credential exposure, injection risk, auth bypass	`Kind/Security`

Priority/* (urgency):

Signal in context	Label
"blocking", "critical", "urgent", production-down	`Priority/Critical`
"soon", "high priority", "should do this sprint"	`Priority/High`
No urgency signal present	`Priority/Medium` (default)

Status/* (workflow state):

Signal in context	Label
Explicit statement that the work is blocked on something else	`Status/Blocked`

Procedure

Read the conversation context (issue/PR title, body, or the triggering discussion) for the signals above.
Call label_read method: "list_repo_labels" (see references/labels.md) to get the current label set with IDs — inference must never guess an ID, only a name, then resolve it. Because exclusive is an org-labels-only flag, this taxonomy plausibly lives at org scope too: for any inferred name absent from the repo pool, also call label_read method: "list_org_labels" with org set to the repo's owner before treating it as unresolved. A failure there means the owner is a user account, not an organisation, so no org pool exists and the name is genuinely absent.
Match inferred label names against the resolved list (case-insensitive). If a scope group already has a different label applied on the target and a new one is inferred for that same scope, plan to replace rather than add (see above).
Low-confidence inference omits the label. If no signal confidently maps to a Kind/* value, do not guess — omit Kind/* entirely rather than default to one. Priority/Medium is the one exception: it's the explicit default when no urgency signal is present, not a guess.
Hand the resolved IDs (plus which scopes to replace) to the caller's issue_write/ pull_request_write call — this skill does not apply labels to an issue or PR itself.

3.8 KiB Raw Blame History

Label inference guide

Scoped labels are mutually exclusive — replace, don't stack

Signal → label mapping

Procedure

3.8 KiB

Raw Blame History