feat(aidd-orchestrator): react to failing CI checks and quality-gate feedback
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- ci-cd
Research direction
Start in plugins/aidd-orchestrator/skills/00-async-dev/actions/review/, especially 01-collect-comments and 03-fix-iteration, and trace how review signals reach the fix loop. Check the existing gh pr checks interaction and comment filtering, then verify that failing checks and quality-gate findings trigger iterations while genuine bot noise remains filtered. Done means the orchestrator cannot finalize a PR with red checks.
Written by the indexing model from the issue text.
Description
Problem
aidd-orchestrator reviews a pull request by reading human comments, and only human comments. Its loop lives in plugins/aidd-orchestrator/skills/00-async-dev/actions/review/ (01-collect-comments, 03-fix-iteration).
Two signals are ignored:
- CI status. A red check does not trigger anything. The orchestrator will happily finalize a PR whose build is broken.
- Quality-gate feedback. Sonar comments are filtered out as bot noise, so its findings never reach the fix loop.
Scope
- Read
gh pr checksand detect failing checks. - Stop discarding quality-gate comments as bot output; route them into the fix loop.
- Iterate a fix on either signal, the same way a human comment does today.
Acceptance criteria
- A failing CI check triggers a fix iteration.
- A quality-gate finding triggers a fix iteration.
- The orchestrator never finalizes a PR whose checks are red.
- Genuine bot noise is still filtered; only quality-gate output gets through.
Origin
Backlog audit 2026-05-21 (aidd_docs/tasks/2026_05/2026_05_21-backlog-audit-and-roadmap.md). Replaces the old #80.
- Dominant language
- TypeScript
- Stars
- 481
- Forks
- 45
- Avg merge
- 14h 27m
- Merged PRs (30d)
- 111
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ai-driven-dev/framework
-
refactor(aidd-orchestrator): the check zone says when to stop, and reviews its axes in one round Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ai-driven-dev/framework#887 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ai-driven-dev/framework#873 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ai-driven-dev/framework#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ai-driven-dev/framework#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ai-driven-dev/framework#467 · 1 comment ·
All issues in ai-driven-dev/framework
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100