skills/inbox/SKILL.md
Triage and review all open GitHub issues and PRs against project templates and contribution guidelines
npx skillsauth add jnuyens/gsd-plugin gsd:inboxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Flow: Detect repo → Fetch open issues + PRs → Classify each by type → Review against template → Report findings → Optionally act (label, comment, close) </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/inbox.md </execution_context>
<context> **Flags:** - `--issues` — Review only issues (skip PRs) - `--prs` — Review only PRs (skip issues) - `--label` — Auto-apply recommended labels after review - `--close-incomplete` — Close issues/PRs that fail template compliance (with comment explaining why) - `--repo owner/repo` — Override auto-detected repository (defaults to current git remote) </context> <process> Execute the inbox workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/inbox.md end-to-end. Parse flags from arguments and pass to workflow. </process>testing
Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.
tools
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
tools
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
testing
Extract decisions, lessons, patterns, and surprises from completed phase artifacts