n8n Workflow: AI Council GitHub Issue Reviewer + BVC Fix Plan
n8n Workflow: AI Council GitHub Issue Reviewer + BVC Fix Plan
Regular price
£18.99
Regular price
£18.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n Workflow: AI Council GitHub Issue Reviewer + BVC Fix Plan
Regular price
£18.99
Regular price
£18.99
Sale price
Unit price
/
per
Turn GitHub issues into a structured AI fix plan—without losing auditability
This n8n workflow reads a GitHub issue (plus up to six repository files at a specific commit), runs a multi-role AI discussion to analyze the problem, and produces a human-reviewable Project Plan bug-fix proposal with a technical audit of routing and token usage.
What this workflow does
- Collects inputs from an n8n form (or manual execution): GitHub owner/repo, issue number, commit SHA, and up to six file paths to read.
- Validates configuration and builds GitHub REST API URLs for the issue, commit, and each selected file at the resolved commit SHA.
- Fetches evidence from GitHub: issue details, commit context, and file contents—while validating size/content limits before packaging the results.
-
Runs structured multi-role analysis using your chosen LLM provider API (DeepSeek/OpenAI/Anthropic/Gemini/Yandex or compatible):
- Architect, Developer, Reviewer, and Tester roles analyze the same evidence and produce independent, structured recommendations.
- Optionally applies BVC: if enabled, it evaluates whether an additional critique round is worth remaining call budget and may execute a second round to reduce disagreement.
- Outputs a fix plan + audit: generates a planning-only “Project Plan” style proposal and compiles an audit of calls, routing, and token usage. Results are returned as HTML (form) or as markdown/audit (manual runs).
Use cases
- SaaS ops teams triaging GitHub issues and needing a consistent fix plan.
- Automation engineers turning bug reports into review-ready proposals for developers.
- Teams comparing AI perspectives (architect/developer/reviewer/tester) to reduce missed edge cases.
Technical details
- GitHub integration via REST API with read-only HTTP Header Auth (e.g., a GitHub token in an Authorization header).
- LLM provider support: DeepSeek/OpenAI/Anthropic/Gemini/Yandex or compatible APIs.
- n8n nodes used: if, set, code, form, sticky note, form trigger.
