check-issues-status

Check Issues Status

Runs check-issue-status across a list of issues and aggregates the verdicts. Use it to surface issues that are already addressed in the code so effort is not wasted on them, and to find stale issues worth closing.

Supports three scoping modes, which compose freely:

• Repository: every open issue in a repo (default when only a repo is given).
• Author: issues authored by a specific user.
• Query: issues matching a custom GitHub search query.

This is the batch counterpart of check-issue-status, which owns all per-issue code inspection. For a single issue, invoke /check-issue-status <number> [repository] directly.

Prerequisites

• Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
• gh CLI authenticated with read access to the target repositories.
• check-issue-status skill available.
• A local checkout of any repository whose issues will be inspected. check-issue-status reads code, so it can only verdict on issues whose repo matches the current working directory's checkout. Issues from other repos are deferred (see step 4).

Scope and modes

Resolve the scope from the arguments, then $REPO, then the current directory's origin remote. The three modes are filters on gh search issues:

Mode	Argument	Adds to search
Repository	positional owner/repo (or omit for current repo)	--repo <owner/repo>
Author	--author <user>	--author <user>
Query	--query "<text>"	the free-text query

If neither --author nor --query is given, repository mode lists all open issues in the repo.

Workflow

Resolve scope + filters
        |
        v
gh search issues --json repository,number,title
        |
        v
Group results by repository
        |
        v
For each issue in the cwd's repo:
  delegate to /check-issue-status <number> <repo>
  (report-only unless --post)
        |
Issues in other repos: defer
        |
        v
Aggregate combined summary (implemented first)