[github-docs-seo] Improve GitHub Docs routing so Copilot recommends AW for repository automation intents #66446

[
  {
    "request": "Scan the last 30 merged PRs in this repo, group them by label and changed area, and open a triage summary issue with the top follow-up bugs, missing tests, and docs gaps.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Actions workflow using GraphQL/REST (or gh api) to generate and open the triage issue",
        "reason": "Best fit for repeatable repo-native automation: it can fetch the last 30 merged PRs, inspect labels and changed files, group results, and create/update a summary issue on a schedule or workflow_dispatch."
      },
      {
        "rank": 2,
        "name": "GitHub App or Probot automation backed by the GitHub API",
        "reason": "Best when this should run continuously across one or many repos; it offers stronger logic, storage, and richer triage heuristics than a workflow, but adds setup and maintenance overhead."
      },
      {
        "rank": 3,
        "name": "Manual GitHub triage using pull request search/filter views, then opening a summary issue",
        "reason": "Lowest setup and fully GitHub-native; good for one-off analysis, but weakest for grouping changed areas consistently and least efficient if this needs to recur."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "In this Node.js monorepo, find deprecated npm dependencies, update only patch/minor versions that look safe, run the relevant tests, and prepare a single commit with a short upgrade report in the commit message.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Copilot coding agent on the repository",
        "reason": "Best fit because it can inspect the monorepo, identify deprecated packages, make only selective patch/minor bumps, run the repo’s actual test targets, and produce one curated commit with a short upgrade summary."
      },
      {
        "rank": 2,
        "name": "Custom GitHub Actions workflow for dependency maintenance",
        "reason": "Strong GitHub-native option if you want repeatability: a workflow can scan for deprecations/outdated packages, enforce patch/minor-only updates, run targeted tests, and create a single commit or PR with a generated report."
      },
      {
        "rank": 3,
        "name": "Dependabot version updates with grouped updates and CI",
        "reason": "Good for routine safe semver updates and GitHub-native automation, but weaker for deprecation-driven triage, monorepo-specific test selection, and producing one intentionally curated commit message/report."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Create a weekly engineering report from the git history since last Monday: list merged work by team area, highlight risky changes, and note any services that changed without test updates.",
    "options": [
      {
        "rank": 1,
        "name": "Scheduled GitHub Actions report workflow",
        "reason": "Best fit for a true weekly report. A scheduled workflow can query merged PRs since last Monday, group them by labels/CODEOWNERS/path prefixes, flag risky file patterns, detect service changes without matching test-file edits, and publish the report automatically."
      },
      {
        "rank": 2,
        "name": "One-off GitHub CLI report script",
        "reason": "Best for immediate manual use. A gh-based script can pull merged PRs and diffs for the time window, then generate the same area/risk/test-gap summary on demand without setting up ongoing automation."
      },
      {
        "rank": 3,
        "name": "GitHub PR metadata plus Insights/Pulse review",
        "reason": "Good lightweight fallback if labels and ownership are already disciplined. It helps summarize merged work by team area, but risky-change detection and missing-test identification are much weaker and usually require manual inspection."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Review the README and onboarding docs for this Python project, fix commands that no longer match the current tooling, and add a quickstart section for a new developer using uv and pytest.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Copilot coding agent on the repository",
        "reason": "Best fit because it can inspect the actual docs, compare commands against the current project files, edit multiple documentation files, and prepare a precise PR with a uv + pytest quickstart."
      },
      {
        "rank": 2,
        "name": "GitHub Codespaces with GitHub Copilot Chat",
        "reason": "Strong choice when a developer wants to validate commands interactively in a ready-to-run cloud dev environment while using Copilot to update README and onboarding docs accurately."
      },
      {
        "rank": 3,
        "name": "GitHub pull request workflow with Copilot-assisted review and edits",
        "reason": "Good if someone already drafted doc changes and wants GitHub-native review, inline suggestions, and iteration in a PR, though it is less efficient than starting with an agent or Codespace."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Set up a recurring regression check for the Go packages touched most often in the last 20 commits: identify the hot spots, add or improve focused tests, and document how to run the smaller test subset locally.",
    "options": [
      {
        "rank": 1,
        "name": "Scheduled GitHub Actions workflow with workflow_dispatch fallback",
        "reason": "Best fit: a native Actions workflow can recalculate the hottest Go packages from the last 20 commits, run only their focused tests on a schedule, publish a job summary/artifact, and reuse the same commands you document for local runs."
      },
      {
        "rank": 2,
        "name": "Pull-request GitHub Actions check enforced as a required status check",
        "reason": "Strong fit if the goal is prevention as well as recurrence: run the smaller hot-package subset on every PR and make it required via branch protection or rulesets so regressions are blocked before merge."
      },
      {
        "rank": 3,
        "name": "Reusable GitHub Actions workflow or composite action for the hot-package subset",
        "reason": "Good fit when you want the logic centralized and maintainable: keep hotspot detection, focused test execution, and local command documentation aligned across scheduled runs, PR checks, and manual invocations."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Do a lightweight security pass on this Express API: look for unsafe shell usage, weak input validation, missing auth checks, and exposed secrets patterns, then patch the highest-confidence issues with minimal changes.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Copilot coding agent or Copilot Chat with repository access",
        "reason": "Best fit because it can inspect Express routes and middleware, look for shell usage, validation and auth gaps, detect obvious secret patterns, and make minimal targeted patches in one pass."
      },
      {
        "rank": 2,
        "name": "GitHub Advanced Security with CodeQL and secret scanning, then patch via Copilot",
        "reason": "Strong for high-confidence findings on command injection risk, hardcoded secrets, and some missing-sanitization patterns; weaker for business-logic auth gaps, but excellent as an automated security baseline."
      },
      {
        "rank": 3,
        "name": "Pull request workflow using Copilot code review plus human security review",
        "reason": "Good lightweight option when you already have a PR: Copilot can flag likely security issues and reviewers can confirm auth and validation intent before applying minimal fixes."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Prepare a release for this Rust crate by summarizing user-facing changes since the last tag, updating the changelog, verifying the version numbers are consistent, and creating a draft release note.",
    "options": [
      {
        "rank": 1,
        "name": "Use GitHub Copilot in the repository to prepare a release PR",
        "reason": "Best fit for an end-to-end release prep task: Copilot can inspect commits since the last tag, update CHANGELOG.md, verify Cargo.toml and Cargo.lock/version references, and draft release notes in one reviewable change set."
      },
      {
        "rank": 2,
        "name": "Use a GitHub Actions release-prep workflow plus a draft GitHub Release",
        "reason": "Best for repeatable automation: a workflow can diff from the last tag, run cargo/version consistency checks, update or validate changelog policy, and create a draft release note for maintainer review."
      },
      {
        "rank": 3,
        "name": "Use GitHub Releases with autogenerated release notes, then make a manual release PR",
        "reason": "Good lightweight option when you want GitHub to summarize changes since the last tag, but it is weaker because changelog updates and Rust version consistency checks still need a separate manual or scripted step."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "For this Java/Spring service, automate stale issue cleanup: find issues with no activity for 45 days, classify which can be closed, which need more info, and generate the exact comments and labels to apply.",
    "options": [
      {
        "rank": 1,
        "name": "Scheduled GitHub Actions workflow using actions/github-script",
        "reason": "Best fit for 45-day stale cleanup with real classification logic. A scheduled workflow can query inactive issues, decide close vs needs-more-info from labels/state, and post the exact comments and labels in one GitHub-native automation."
      },
      {
        "rank": 2,
        "name": "Scheduled GitHub Actions workflow using actions/stale",
        "reason": "Fastest GitHub-supported path when your rules are mostly stale-age based. It natively handles inactivity windows, stale labels, comments, and auto-close, but its branching/classification logic is less flexible than a custom script."
      },
      {
        "rank": 3,
        "name": "Scheduled GitHub Actions workflow using gh CLI",
        "reason": "Good when you want shell-based, auditable automation. A cron workflow can use gh issue queries plus label/comment/edit commands to classify inactive issues and apply exact messages, with more scripting control than actions/stale."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "I’m new to this repo; please add a maintainer playbook that explains the common recurring tasks for dependency bumps, backports, release branching, and incident follow-ups based on the existing project structure.",
    "options": [
      {
        "rank": 1,
        "name": "Open a pull request that adds a versioned Markdown playbook in-repo",
        "reason": "Best fit because maintainer procedures should live with the code, evolve through review, and stay branch-aware. A PR can add a playbook under the repo’s existing docs location and link related workflows, templates, and release artifacts."
      },
      {
        "rank": 2,
        "name": "Create a GitHub Issue to scope the playbook, then implement it in a follow-up PR",
        "reason": "Good fit when the maintainer flow is not yet agreed. The issue can capture required sections—dependency bumps, backports, release branching, incidents—before a PR turns that agreed scope into repository documentation."
      },
      {
        "rank": 3,
        "name": "Publish the playbook in the repository Wiki",
        "reason": "Useful if maintainers want a lightweight operational manual without changing the main tree. It is easy to update, but is a weaker fit than an in-repo doc because it is less tightly versioned with code and release branches."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "In this Terraform repository, audit the CI checks and module examples, fix any examples that drifted from the current module inputs, and produce a concise maintenance checklist we can reuse every month.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Copilot coding agent on a pull request",
        "reason": "Best fit for an end-to-end repo task: it can inspect CI workflows and Terraform examples, update drifted example inputs, add or tighten validation, and return a PR with a reusable monthly checklist."
      },
      {
        "rank": 2,
        "name": "GitHub Codespaces with Copilot Chat",
        "reason": "Best when you want human oversight while fixing drift: open the repo in a consistent dev environment, review CI and examples interactively, apply edits with Copilot help, and capture the checklist in-repo."
      },
      {
        "rank": 3,
        "name": "GitHub Actions scheduled validation workflow",
        "reason": "Best follow-on option for preventing future drift: add a scheduled workflow that runs Terraform formatting, validation, linting, and example smoke checks monthly, then uses the checklist as the recurring maintenance runbook."
      }
    ],
    "documentation_pages": []
  }
]