Process Issue

Process a GitHub Issue as a maintainer, from triage and ownership routing through dependencies and evidence-based closure. Use to manage an Issue's next step; use fix-issue for implementation.

49 stars 102 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add hw-native-sys/simpler --skill process-issue
Manual install
git clone --depth 1 https://github.com/hw-native-sys/simpler.git /tmp/simpler
mkdir -p ~/.claude/skills
cp -r /tmp/simpler/.claude/skills/process-issue ~/.claude/skills/process-issue

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Process an Issue as maintainer

Accept an Issue number or URL, or an explicitly scoped set of Issues. Resume
from current GitHub state instead of repeating triage on every invocation.
GitHub is the business record; do not register a duplicate task in another queue.

When called by [maintainer](../maintainer/SKILL.md), preserve its selected write
scope, authority and observation context. Linked items outside that scope remain
read-only; return the result to the caller without starting another maintenance loop.
Developers may use this workflow for their own scope without acquiring maintainer
permissions or taking over other contributors' work.

## Read the current situation

Use [GitHub setup](../../lib/github/setup.md) to identify repository and account.
Write access is not authorization to change ownership, publish messages or close
Issues: stay within the requested maintenance scope and reuse authorization already
given. For an analysis-only request, recommend actions without writing to GitHub.

Read the body, comments, assignees, labels, parent/sub-Issues, explicit blocking
relations and linked PRs, including drafts. Paginate connections when necessary.
Check current main and related open or recently merged PRs before assigning new
implementation. Compare scope and evidence, not just matching titles.

Use current repository ownership guidance, CODEOWNERS if present, and the relevant
track's latest body. The simpler
Read the full skill on GitHub

Details

Skill name
process-issue
Path
.claude/skills/process-issue/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Process Issue skill do?

Process a GitHub Issue as a maintainer, from triage and ownership routing through dependencies and evidence-based closure. Use to manage an Issue's next step; use fix-issue for implementation.

How do I install the Process Issue skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add hw-native-sys/simpler --skill process-issue. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Process Issue popular?

It lives in hw-native-sys/simpler, which has 49 GitHub stars and 102 forks.

Related skills

Benchmark

49

hw-native-sys/simpler

Benchmark runtime performance on hardware. If the current branch has commits ahead of upstream/main or uncommitted changes, compares against the fork point (merge-base). Otherwise benchmarks current state only. Use when the user asks to benchmark, measure performance, or compare latency.

Git & Code Review102

Checkout PR

49

hw-native-sys/simpler

Add a remote for a given PR's head repository and checkout a local pr-xxx-work branch. Use when the user wants to work on someone else's PR locally.

Git & Code Review102

Clean Branches

49

hw-native-sys/simpler

Remove stale local and remote git branches that have been merged into main. Detects regular merges and squash merges. Cleans up fork remote branches and prunes tracking refs. Use when the user asks to clean up branches, remove merged branches, or tidy up git.

Git & Code Review102

Process PR

49

hw-native-sys/simpler

Process a GitHub PR as a maintainer, routing review, following revisions, checking merge readiness and reconciling linked Issues. Use for PR lifecycle management; use review-pr for technical review and fix-pr for author-side repairs.

Git & Code Review102

Multi Repo Setup

49

hw-native-sys/simpler

Set up a cross-repo investigation when a workload from another repo (pypto, pypto-lib, pypto-serving, etc.) needs to be run, especially when you want to swap in simpler-main HEAD or the current worktree's simpler instead of the version that repo pins. Documents the repo graph (who imports who), clones-or-updates each external repo every invocation so stale local clones don't lie about CI parity, and points at each repo's own skills/docs for workload-specific steps. MUST invoke before chasing "X doesn't work on simpler" reports where X lives outside this repo.

Git & Code Review102

Review PR

49

hw-native-sys/simpler

Review a GitHub PR or a fixed commit range from its background, existing pain points, and expected benefits through correctness, architecture, decoupling, performance, code quality, and repository standards. Uses the correct diff (fixed range or merge-base) and checks claims against implementation and evidence. Optionally folds in independent reviews from local `codex` / `claude` CLIs or read-only sub-agents when the invocation explicitly opts in. Use when the user asks to review a PR, a fixed range, or changes.

Git & Code Review102

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.