Capability-aware GitHub app routing for Next.js and audit-focused debugging flows

The current GitHub app/skill routing can steer agents toward GitHub-specific capabilities even when they are not relevant to the user task, and it can also add unnecessary context when the user is debugging a local web app.

A recent example in chat involved a Next.js frontend issue where the real problem was a React asChild warning in src/components/ui/button.tsx and a separate npm audit report. The GitHub app toolset was not needed for that workflow, but the agent still invoked GitHub-related tooling because the conversation context included a developer instruction mentioning the GitHub plugin.

Request:

• Make GitHub-app routing capability-aware and task-aware.
• Prefer local reasoning or direct file inspection when the user is debugging their own app code, package.json, or npm audit output.
• Avoid surfacing GitHub tooling unless the user explicitly asks about GitHub, a repo, a PR, an issue, or another GitHub-hosted artifact.
• Ensure security-audit and dependency-debugging workflows do not default to GitHub tooling when the repo context is already fully local.

This would reduce confusion and keep the tool selection aligned with the actual task.