Show HN: Aido – an AI companion for the pull requests your AI writes

Aido, an AI companion for pull requests authored by AI agents such as Copilot, Claude Code, and Cursor, automatically explains, summarizes, reviews, and documents changes, keeping humans in the loop. The tool runs inside GitHub Actions with a single workflow file, supports on-demand commands on any PR or issue, and works with Gemini, ChatGPT, or Claude via bring-your-own-key. Aido aims to help developers quickly understand code they did not write, addressing the growing volume of AI-generated pull requests.

The AI companion for the pull requests your AI writes. AI agents — Copilot, Claude Code, Cursor — are opening more and more pull requests, and a human still has to understand code they didn't write. Aido keeps that human in the loop: when an AI-authored PR lands, it can automatically explain, summarize, review, and document the change. And you can run those same commands on any PR or issue on demand — just comment aido <command . One companion, the whole review lifecycle: review, summarize, explain, document, test, and triage — with Gemini, ChatGPT, or Claude , right inside GitHub Actions. Install with a single workflow file. - 🤖 Auto-companion for AI-authored PRs — when Copilot / Claude Code / Cursor open a PR, Aido runs automatically explain + summarize by default; review/docs/test opt-in - ⚡ On-demand on any PR or issue — aido review , summarize , explain , docs , suggest , test , triage - 🧩 Consolidated, persona-guided reviewer with applyable inline suggestions robust validation, zero false positives - 🔌 Multi-provider, bring-your-own-key: Gemini default , ChatGPT, Claude — no third-party data processor - 📦 One-file install from a pinned release tag; upgrading is a one-line bump - 🔧 Fully configurable prompts, personas, tones, and per-command models Secrets add under Settings → Secrets and variables → Actions : GEMINI API KEY required for default provider CHATGPT API KEY if using ChatGPT CLAUDE API KEY if using Claude - Uses the built-in for posting comments and reviews. GITHUB TOKEN ⚠️ Forked PRs : repository secrets may be unavailable due to GitHub policy. Comment these on any PR: aido review → Multi-persona code review + digest aido summarize | aido sum | aido summary → High-level PR summary for stakeholders aido explain → Developer-focused step-by-step explanation aido docs → Draft/augment documentation aido suggest | aido improve → Safe improvement ideas aido test → Structured test plan, coverage gaps, and follow-up tasks aido config-check → Validate configs Comment these on any issue: aido triage → Classify, suggest labels, find similar issues, recommend next steps When an AI agent Copilot, Claude Code, Cursor, … opens a pull request, Aido can run automatically — no comment needed — so a human can quickly understand and digest code they didn't write. - Add .github/workflows/aido-auto.yml copy-based or examples/remote/aido-auto.yml remote install . - Configure which authors trigger it and which commands run in .github/scripts/auto/aido-auto-config.json . Companion-first defaults: explain + summarize . Add review , docs , or test to the commands list to run more. Only AI-authored PRs trigger it per aiAuthors ; human PRs are never auto-run. It fires on PR open/reopen/ready — not on every commit . Per-PR opt-out: add a no-aido label configurable via skipLabels or put < -- aido: skip -- in the PR body to skip a single PR — no config change needed.- Fires on pull request not pull request target , so forked PRs stay safe read-only token, no secrets . // .github/scripts/auto/aido-auto-config.json { "enabled": true, "aiAuthors": "copilot", "claude-code bot ", "cursor bot " , "commands": "explain", "summarize" , "skipLabels": "no-aido" , } Note: github-actions bot and dependabot bot are excluded by default — the former is too broad, and Dependabot PRs run with a read-only token and no repo secrets, so Aido can't act on them. Add them explicitly at your own risk. Prefer to control exactly when Aido runs? Add it as a step in your own workflow — the Marketplace-published composite action: - uses: aido-dev/aido@v1 with: command: review review | summarize | explain | docs | suggest | test | triage pr number: ${{ github.event.pull request.number }} env: GITHUB TOKEN: ${{ secrets.GITHUB TOKEN }} GEMINI API KEY: ${{ secrets.GEMINI API KEY }} For triage , pass issue number instead of pr number . See examples/action/ /aido-dev/aido/blob/main/examples/action for full workflows. Two ways to run Aido — pick per use case: Reusable workflows / one-file install below → the comment-driven UX aido review on a PR and auto-run on AI-authored PRs.This composite action→ run a specific command as a step, on your own triggers e.g. review every PR on pull request . - Add repository secrets: GEMINI API KEY default provider CHATGPT API KEY if using ChatGPT CLAUDE API KEY if using Claude - Copy to examples/remote/aido.yml .github/workflows/aido.yml — a single thin workflow that runs Aido from a pinned release tag. Upgrading is a one-line tag bump. - Comment aido review on a PR. - Optional Customize any command by adding its config file e.g. .github/scripts/review/aido-review-config.json — overrides the shipped defaults, no scripts needed. Seefor details. examples/remote/ - Add repository secrets as above . - Commit workflows .github/workflows/ and scripts .github/scripts/ .⚠️ Make sure to include .github/scripts/lib/ — all command scripts depend on this shared library. - Comment aido review on a PR. - Optional Customize configs in aido- -config.json — or the prompts and scripts themselves. - Audience: - Summarize: stakeholders product/engineering leadership - Explain: developers/reviewers - Depth: - Summarize: high-level intent, scope, risks, impact; no implementation details - Explain: step-by-step mechanics, rationale, risks, verification - Content constraints: - Summarize: no code blocks, diffs, or inline suggestions; concise and skimmable - Explain: may include tiny illustrative snippets only if essential; avoid suggestions and large blocks As more of your PRs are written by AI, Aido makes sure a human still understands them — automatically, and on demand. It's practical, configurable, and team-friendly: save time, catch issues early, and keep everyone in the loop — without leaving GitHub. Dispatcher: .github/workflows/aido-dispatch.yml Parses the first line of the comment, normalizes it, and routes to the right reusable workflow. Reusable workflows invoked via workflow call : .github/workflows/aido-review.yml .github/workflows/aido-summarize.yml .github/workflows/aido-explain.yml .github/workflows/aido-docs.yml .github/workflows/aido-suggest.yml .github/workflows/aido-test.yml .github/workflows/aido-triage.yml issues Each workflow builds a prompt from PR context title, body, changed files, truncated diff ~15k chars , calls the selected provider/model, and posts a PR review with inline, applyable suggestions when applicable , validated by a robust layer to ensure safety and accuracy . Shared library required by all commands : .github/scripts/lib/ providers.js — AI provider wrappers ChatGPT / Gemini / Claude , model resolution github.js — GitHub API client, event parsing, PR context fetchers, comment posting config.js — JSON config loading with defaults and deep merge text.js — truncation, files summary, prompt templates, comment footers Review: - Script: .github/scripts/review/aido-review.js - Config: .github/scripts/review/aido-review-config.json object with { reviewer, personas } ; reviewer sets provider/model; personas guide facets - Script: Summarize stakeholder-facing; aliases: summarize | sum | summary :- Script: .github/scripts/summarize/aido-summarize.js - Config: .github/scripts/summarize/aido-summarize-config.json - Script: Explain developer-focused : - Script: .github/scripts/explain/aido-explain.js - Config: .github/scripts/explain/aido-explain-config.json - Script: Docs: - Script: .github/scripts/docs/aido-docs.js - Config: .github/scripts/docs/aido-docs-config.json - Script: Suggest: - Script: .github/scripts/suggest/aido-suggest.js - Config: .github/scripts/suggest/aido-suggest-config.json - Script: Test: - Script: .github/scripts/test/aido-test.js - Config: .github/scripts/test/aido-test-config.json adds testFocus for unit / integration / e2e / regression / performance / security / accessibility - Script: Triage issues : - Script: .github/scripts/triage/aido-triage.js - Config: .github/scripts/triage/aido-triage-config.json adds candidateLabels , severityLabels , and applyLabels to optionally auto-apply suggested labels; default false - Script: Each config supports: provider CHATGPT|GEMINI|CLAUDE , model , language , tone , style , length , include title/body/filesSummary/diff , additionalInstructions , and an optional promptTemplate with placeholders. - Use a single consolidated reviewer informed by your configured personas in aido-review-config.json .- Top-level reviewer chooses provider/model and optional context checks . personas define roles with prompt/tone/style/language to guide faceted notes. - Top-level - The review body contains a clean summary, recommendation, faceted notes, and optional context checks. - All code changes are delivered as inline PR review suggestions with “Apply suggestion” buttons , thoroughly validated for safety and actionability — not in the body. Keep it reasonable: start with 3–5 personas e.g., pedagogy, architecture, security, performance, QA . Pre-curated packs: see /examples/.github/review/example personas/ example-personas.json ~50 personas great defaults-personas.json balanced starter set - Topic packs: web frontend- .json , cloud and devops- .json , security- .json , and more. - Prefer short, focused prompts and configs. - Use aido config-check if things look off. - For UI work, pair aido explain with aido suggest . - For releases, run aido summarize → aido docs . - Before merging, run aido test to surface missing test cases and coverage gaps. - For new issues, run aido triage to get a quick classification, label suggestions, and similar-issue links. - Diff is truncated ~15k chars to keep prompts efficient. - Provider/model availability and naming can change; set explicit models in configs. - Forked PRs may lack secrets → provider calls may be skipped. github-actions · ai-code-review · ai-assistant · developer-productivity · persona-based-reviews · openai · gemini · claude · chatgpt · pr-bot · automated-code-review Happy shipping ✨ Note Data handling: - Prompts, code, and metadata may be sent to external AI services and could be logged or retained by those providers. - Do not include secrets, confidential, or regulated data unless you fully trust the operator and provider. Reliability: - Providers can rate‑limit, change models/behavior, or go offline without notice. - Do not depend on AI outputs for production without human review and validation. Accuracy: - AI models can be incorrect, outdated, or hallucinate details. - Always verify explanations, reviews, and code suggestions before applying.