woodpecker-trigger-discipline claims 4 trigger phrases now registered to cluster:ci-agent #9

New Issue

2026-08-16T02:06:54+03:00

oleks commented

2026-08-16 02:06:54 +03:00

Why: fleet-govern's registry/ownership.yaml decided by 30-day usage (ci-agent 202 events vs. 0 for this skill) that these 4 trigger phrases belong to cluster:ci-agent: "why won't this pr merge", "required check never runs", "pr is blocked but ci is green", "should i force-merge". woodpecker-trigger-discipline still declares them in its own description, creating an overlap that routes ambiguously.

Acceptance:

Drop the 4 overlapping phrases from woodpecker-trigger-discipline's SKILL.md description, deferring to cluster:ci-agent (which already routes correctly there)
OR: if this skill should retain ownership, contest the registry row in fleet-govern's registry/ownership.yaml with a maintainer decision

Links: fleet-govern registry/ownership.yaml (session eca8b169, 2026-08-16). Evidence: ~/projects/claude-plugins/fleet-govern/references/fleet-map.md and bin/fleet-govern check-ownership output.

**Why**: fleet-govern's registry/ownership.yaml decided by 30-day usage (ci-agent 202 events vs. 0 for this skill) that these 4 trigger phrases belong to cluster:ci-agent: "why won't this pr merge", "required check never runs", "pr is blocked but ci is green", "should i force-merge". woodpecker-trigger-discipline still declares them in its own description, creating an overlap that routes ambiguously. **Acceptance**: - [ ] Drop the 4 overlapping phrases from woodpecker-trigger-discipline's SKILL.md description, deferring to cluster:ci-agent (which already routes correctly there) - [ ] OR: if this skill should retain ownership, contest the registry row in fleet-govern's registry/ownership.yaml with a maintainer decision **Links**: fleet-govern `registry/ownership.yaml` (session eca8b169, 2026-08-16). Evidence: ~/projects/claude-plugins/fleet-govern/references/fleet-map.md and bin/fleet-govern check-ownership output.

oleks added the bug label 2026-08-16 02:06:54 +03:00

oleks added the agent/wip label 2026-08-16 02:11:17 +03:00

oleks added this to the claude-plugin-cicd-insights-board project 2026-08-16 02:11:18 +03:00

oleks referenced this issue from a commit

2026-08-16 02:16:55 +03:00

fix(woodpecker-trigger-discipline): cede 4 diagnostic phrases to cluster:ci-agent per registry (oleks/claude-plugin-cicd-insights#9), v1.4.8

oleks referenced this issue from a commit

2026-08-16 02:17:36 +03:00

fix(woodpecker-trigger-discipline): don't quote the ceded phrases in the description (oleks/claude-plugin-cicd-insights#9), v1.4.9

oleks commented

2026-08-16 02:32:58 +03:00

Done — took option 1 (defer to the registry). cicd-insights v1.4.8 (fix(woodpecker-trigger-discipline)…) drops "why won't this PR merge", "PR is blocked but CI is green", "required check never runs", "should I force-merge" from the skill description; v1.4.9 removes even the quoted mention of them (fleet-govern's check-ownership scans quoted phrases in descriptions, so naming them in a "these belong to ci-agent" note re-tripped the duplicate-claim block).

cluster:ci-agent already hands off to this skill by name (agents/ci.md:164), so the routing path is ci-agent → woodpecker-trigger-discipline, matching the registry's "skill should be reached via ci-agent" note. bin/fleet-govern check-ownership no longer reports any cicd-insights duplicate-claim rows.

Done — took option 1 (defer to the registry). cicd-insights **v1.4.8** (`fix(woodpecker-trigger-discipline)…`) drops "why won't this PR merge", "PR is blocked but CI is green", "required check never runs", "should I force-merge" from the skill description; **v1.4.9** removes even the quoted mention of them (fleet-govern's `check-ownership` scans quoted phrases in descriptions, so naming them in a "these belong to ci-agent" note re-tripped the duplicate-claim block). `cluster:ci-agent` already hands off to this skill by name (`agents/ci.md:164`), so the routing path is ci-agent → woodpecker-trigger-discipline, matching the registry's "skill should be reached via ci-agent" note. `bin/fleet-govern check-ownership` no longer reports any cicd-insights duplicate-claim rows.

oleks closed this issue

2026-08-16 02:33:00 +03:00

oleks added spent time 24 minutes

2026-08-16 02:35:03 +03:00

oleks commented

2026-08-16 02:35:03 +03:00

oleks added agent/worked:oleks/50fd9d79 agent/worked:oleks/50fd9d79:24min and removed agent/wip labels 2026-08-16 02:35:05 +03:00

repo-worker commented

2026-08-16 02:37:53 +03:00

Already resolved on main: woodpecker-trigger-discipline's description no longer claims the 4 phrases owned by cluster:ci-agent, and now names the hand-off explicitly ("The merge-blocked / force-merge diagnostic entry points are owned by cluster:ci-agent, which hands off here"). Verified fleet-govern check-ownership --quiet reports 0 blocking findings for this pair.

Resolving commits: 6df8f6f (cede the 4 phrases, v1.4.8), 6f9feef (unquote the ceded phrases in the description, v1.4.9).

Already resolved on `main`: `woodpecker-trigger-discipline`'s description no longer claims the 4 phrases owned by `cluster:ci-agent`, and now names the hand-off explicitly ("The merge-blocked / force-merge diagnostic entry points are owned by cluster:ci-agent, which hands off here"). Verified `fleet-govern check-ownership --quiet` reports 0 blocking findings for this pair. Resolving commits: 6df8f6f (cede the 4 phrases, v1.4.8), 6f9feef (unquote the ceded phrases in the description, v1.4.9).

Sign in to join this conversation.

2 Participants

Notifications

Total Time Spent: 24 minutes

oleks

24 minutes

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: oleks/claude-plugin-cicd-insights#9