Normalize GitHub workflow skill family #15

New issue

Open

opened 2026-08-22 06:49:03 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-22 06:49:03 +00:00

(Migrated from github.com)

Parent: #13

Goal

Turn the prior GitHub workflow pack into a deduplicated set of canonical Agent Skills. This issue owns design/dedupe only until a later RAGE implementation slice consumes it.

Candidates

gh-address-comments
gh-close-superseded-prs
gh-create-issues
gh-fix-ci
gh-issue-loop
gh-issue-work
gh-loop
gh-merge-if-green
gh-publish-pr
gh-triage
gh-workflow

Format gate

Every retained skill must use:

---
name: <lowercase-hyphen-id>
description: keyword, keyword, keyword
compatibility: <only when actually required>
---

Rules:

2–8 comma-separated description keywords, no prose;
concise body, preferably ~80 lines or less;
reference/scripts split for detail or deterministic helpers;
one semantic responsibility per activation boundary;
no copied policy blocks when another canonical skill can be referenced or composed.

Dedupe questions

Resolve before implementation:

Is gh-workflow an umbrella/router, or does it duplicate the narrower skills?
Are gh-loop, gh-issue-loop, and gh-issue-work truly distinct activation/authority scopes?
Should gh-merge-if-green remain separate because it has a strict exact-head/no-UNSTABLE gate?
Can gh-publish-pr, gh-address-comments, and gh-fix-ci remain narrow terminal operations without repeating queue/loop policy?
Does gh-triage own classification only, with mutation delegated elsewhere?

Required semantics

current user request before backlog;
backlog continues while actionable work exists;
no-progress/repeated-failure signatures stop loops;
UNSTABLE, queued, pending, stale, or wrong-head CI never counts as merge-ready;
do not infer permanent write/merge authorization from a loop;
branch/PR state must be inspected before mutation;
do not discard unrelated work or close valid concurrent PRs as cleanup theater.

Acceptance

overlap graph recorded in the issue;
each candidate marked KEEP, MERGE-INTO, or DROP-DUPLICATE with rationale;
retained skill boundaries do not overlap materially;
later implementation can proceed one coherent group at a time without rediscovering the semantics.

Parent: #13 ## Goal Turn the prior GitHub workflow pack into a deduplicated set of canonical Agent Skills. This issue owns design/dedupe only until a later RAGE implementation slice consumes it. ## Candidates - `gh-address-comments` - `gh-close-superseded-prs` - `gh-create-issues` - `gh-fix-ci` - `gh-issue-loop` - `gh-issue-work` - `gh-loop` - `gh-merge-if-green` - `gh-publish-pr` - `gh-triage` - `gh-workflow` ## Format gate Every retained skill must use: ```yaml --- name: <lowercase-hyphen-id> description: keyword, keyword, keyword compatibility: <only when actually required> --- ``` Rules: - 2–8 comma-separated description keywords, no prose; - concise body, preferably ~80 lines or less; - reference/scripts split for detail or deterministic helpers; - one semantic responsibility per activation boundary; - no copied policy blocks when another canonical skill can be referenced or composed. ## Dedupe questions Resolve before implementation: 1. Is `gh-workflow` an umbrella/router, or does it duplicate the narrower skills? 2. Are `gh-loop`, `gh-issue-loop`, and `gh-issue-work` truly distinct activation/authority scopes? 3. Should `gh-merge-if-green` remain separate because it has a strict exact-head/no-UNSTABLE gate? 4. Can `gh-publish-pr`, `gh-address-comments`, and `gh-fix-ci` remain narrow terminal operations without repeating queue/loop policy? 5. Does `gh-triage` own classification only, with mutation delegated elsewhere? ## Required semantics - current user request before backlog; - backlog continues while actionable work exists; - no-progress/repeated-failure signatures stop loops; - `UNSTABLE`, queued, pending, stale, or wrong-head CI never counts as merge-ready; - do not infer permanent write/merge authorization from a loop; - branch/PR state must be inspected before mutation; - do not discard unrelated work or close valid concurrent PRs as cleanup theater. ## Acceptance - overlap graph recorded in the issue; - each candidate marked KEEP, MERGE-INTO, or DROP-DUPLICATE with rationale; - retained skill boundaries do not overlap materially; - later implementation can proceed one coherent group at a time without rediscovering the semantics.