/gen-gh-user-rpt

Generate a GitHub user activity report

Your Role

You are the leader-rpts report launcher. You resolve a person identifier to their GitHub login and delegate data collection and rendering to the report-analyst subagent, which runs in its own context window.

---

Invocation

/leader-rpts:gen-gh-user-rpt <user> [period] [--no-rpt-files]

Examples:

/leader-rpts:gen-gh-user-rpt Doug
/leader-rpts:gen-gh-user-rpt Doug "last 2 weeks"
/leader-rpts:gen-gh-user-rpt alicesmith
/leader-rpts:gen-gh-user-rpt [email protected] "last month" --no-rpt-files

---

Workflow

Step 1 — Parse flags

Scan the raw arguments for --no-rpt-files. If present, set write-file = false and remove it from further argument processing. Otherwise write-file = true.

Step 2 — Locate config and resolve user

Find and read:

Glob: **/leader-rpts/resources/config.json

Resolve <user> in this order:

1. Case-insensitive match on name in users array → use gh-login, full-name
2. Match on gh-login directly → use as-is, set full-name from config or gh-login
3. Match on email → use email to look up the user, ask for gh-login if not in config
4. Unrecognised value that looks like a GH login → use directly, set full-name to login
5. Unrecognised value — ask the user for the GitHub login before proceeding
6. Cannot resolve → ask the user for the GH login or email before continuing

If resolving from a derived or unregistered identifier, offer after the report to run /leader-rpts:add-person to persist them.

Step 3 — Verify GitHub login exists

gh api users/<gh-login> --jq '{login: .login, name: .name}' 2>&1

If not found, surface the error. Ask if the user wants to try a corrected slug.

Step 4 — Resolve period

• If a period argument was provided, parse it to period-start and period-end (YYYY-MM-DD).
• Default: previous two full Monday–Sunday weeks. Compute: find the most recent Sunday on or before today (week-end); subtract 13 days for week-start. Period = week-start to week-end.
• Supported shorthands: "last 2 weeks", "last 30 days", "last month", "Q1 2026", etc.

Step 5 — Derive output filename

Slugify the resolved name: lowercase, replace spaces with hyphens, strip non-alphanumeric characters except hyphens.

output-filename = "gh-user-rpt-<name-slug>.md"

Example: name Doug Clougher → gh-user-rpt-doug-clougher.md

Step 6 — Load template

Read the template file:

Read: **/leader-rpts/templates/gen-gh-user-rpt.md

Step 7 — Run the report in a subagent

Read the report-analyst instructions:

Read: **/leader-rpts/skills/report-analyst/SKILL.md

Use the Agent tool (not the Skill tool) to spawn a subagent. Pass it a self-contained prompt combining the analyst instructions with the resolved context:

<full content of report-analyst SKILL.md>

## Resolved Identifiers
- Full name: <full-name>
- GH login: <gh-login>
- Period: <period-start> to <period-end>
- GitHub org: <gh-org>

## Task
Generate a GitHub user activity report. Follow the generation-rules and template below.

## Template
<full contents of gen-gh-user-rpt.md>

Step 8 — Display and save

Display the returned report to the user.

If write-file = true, write the rendered Markdown to <output-filename> in the current working directory using the Write tool. Inform the user:

"Report saved to <output-filename>"

If write-file = false, skip the file write.

Step 9 — Offer persistence

If the user was resolved from an unregistered identifier, ask: "Would you like to add <full-name> to your config so you don't need to enter their details next time? Run /leader-rpts:add-person."

---

Quality Reminders

• Never run GitHub API calls in the main context — all data collection happens inside the Agent subagent.
• Always confirm derived GH logins before using them.
• Use the Agent tool, not the Skill tool — the report-analyst is not a registered slash command.