feat(aidd-vcs): ci-watch skill with compact GitHub status script
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- github, github-actions
- Ambito
- ci-cd, developer-experience, tooling
Direzione di ricerca
Start by reading plugins/aidd-vcs/skills/02-pull-request/, plugins/aidd-dev/skills/00-sdlc/SKILL.md, and the async review path under plugins/aidd-orchestrator/skills/00-async-dev/actions/review/. Trace the existing ship/finalize flow and inspect how .aidd/config.yml features are handled. Done means the read-only ci-watch script and skill provide tested exit-code behavior, and the flag-enabled ship path blocks success on red checks without changing the default path.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
Ship / open-PR paths do not wait on CI deterministically. Free-form agent polling is verbose and inconsistent. Sessions can treat work as done while checks are still red. The async orchestrator path (#149) does not give interactive sessions a compact exit-code contract.
Not a duplicate of #149
| #149 | This issue | |
|---|---|---|
| Caller | Async bot / orchestrator | Interactive session skill |
| Mechanism | React to checks/comments in bot loop | Local script + skill mapping exit codes |
| Integration | Auto finalize rules | Opt-in via features.ci_watch_before_ship |
Scope
- Skill
ci-watch: resolve PR | branch | run id → run script → map exit code. - Bundled script (GitHub-first), e.g. plugin
scripts/ci-watch:- deps:
gh,jq; - flags:
--repo,--pr|--run|--branch, optional--workflow,--interval; - compact stdout (state-change lines; failed job logs only on red);
- stable exit codes documented in script header + skill (pass / fail / cancelled / other / pass-but-not-merged if merge watch);
- pure classifiers unit-testable without network.
- deps:
- Integration contract (non-vacuous):
- Feature flag
features.ci_watch_before_shipin.aidd/config.yml(default false = non-breaking). - When true, ship/finalize path must run ci-watch and must not claim success on non-zero failure exit.
- When false, skill remains manually invocable (standalone value).
- Feature flag
- Skill does not re-implement polling in prose as the primary path.
Standalone value: Any session can wait on CI with stable exit codes without an async bot.
Acceptance criteria
- Green PR: exit 0; short summary.
- Red PR: non-zero failure; failed check names (+ failed logs only).
- Skill invokes script and maps exit codes (no primary agent poll loop).
- Read-only (no commits / force-push).
- With
features.ci_watch_before_ship: trueand red checks, ship path does not report success (doc + action test or fixture). - With flag false/absent, ship behavior unchanged; skill still runnable alone.
- Issue body states non-duplicate vs #149 (this section).
Prior art in this repo
- #149 — async bot reacts to failing checks / quality gates (
plugins/aidd-orchestrator/skills/00-async-dev/actions/review/) plugins/aidd-vcs/skills/02-pull-request/— open PR / ship-adjacent external pathplugins/aidd-dev/skills/00-sdlc/SKILL.md— ship step in interactive SDLC (no CI wait today)
Relations
Intended graph (same fields as GitHub parent / blocked-by / blocks). Formal GraphQL edges need maintainer write — see comment on #584.
| Field | Value |
|---|---|
| parent | #584 |
| blocked-by | #585 |
| blocks | — |
| related | #149 |
| MVP | 1 |
Out of scope
- Auto-fix on red CI
- Non-GitHub forges in v1 (same exit-code contract later)
- Async bot loop (#149)
- Lingua principale
- TypeScript
- Stelle
- 481
- Fork
- 45
- Merge medio
- 19h 48m
- PR unite (30g)
- 100
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ai-driven-dev/framework
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
ai-driven-dev/framework#940 ·
I maintainer di solito rispondono entro 1 giorno
-
refactor(aidd-orchestrator): the check zone says when to stop, and reviews its axes in one roundAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
ai-driven-dev/framework#887 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
ai-driven-dev/framework#873 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
ai-driven-dev/framework#625 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
ai-driven-dev/framework#467 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di ai-driven-dev/framework
Issue simili
-
bug HemiStake
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
hemilabs/ui-monorepo#2413 ·
I maintainer di solito rispondono entro 1 giorno
-
component/ui framework/react kind/bug language/javascript
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
meshery/meshery#22216 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
company delete fails with 500 on any company that has activity (cost events, inbox dismissals)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
paperclipai/paperclip#14982 ·
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 95/100
lingdojo/kana-dojo#31515 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno