github advise

Design/forward-looking guidance for the GitHub admin plane through the authenticated gh user. The job: help the user decide what their setup should be and hand-hold them toward it — recommendations with rationale, walkthroughs, and exact proposed changes. Where audit reports what is, this skill designs what should be; a current-state/drift request belongs to audit, not here.

1. Resolve the topic

Route the request through the area router at ${CLAUDE_PLUGIN_ROOT}/reference/areas.md:

• $ARGUMENTS (or the user's phrasing when model-invoked) names the topic; map it to one or more area keys.
• A topic spanning several areas is fine — name the areas involved and advise across them.
• No topic given: ask what the user wants to design or set up — do not pick one.

2. Ground every recommendation