// Review recent issues with labeling, context analysis, and duplicate detection
Classify and summarize a PR for efficient review
Create a new es-toolkit release (version bump, changelog, tag)
es-toolkit usage guide covering installation, import patterns, and setup for Node.js, Bun, Deno, and browsers. Use when the user asks how to install, import, or set up es-toolkit in their project.
Guide migrating lodash code to es-toolkit. Use when the user wants to migrate from lodash, replace lodash imports, reduce bundle size by switching to es-toolkit, or understand the difference between es-toolkit and es-toolkit/compat.
Analyze code or requirements and recommend the best es-toolkit functions. Use when the user asks which es-toolkit function to use, needs help finding a utility, or wants alternatives to manual implementations.
Verify compat PR claims by running lodash vs es-toolkit/compat at runtime
| name | issue-review |
| description | Review recent issues with labeling, context analysis, and duplicate detection |
| argument-hint | [count=10] |
| allowed-tools | Bash, Read, Grep, Glob, Skill |
Fetch recent issues, label unlabeled ones with context, detect duplicates.
$ARGUMENTS — Number of issues (default: 10)
Examples:
/issue-review — 10 most recent open issues/issue-review 20 — 20 issuesgh issue list --repo toss/es-toolkit --state open --limit {count} --json number,title,author,labels,createdAt
For each issue:
gh issue view {number} --repo toss/es-toolkit --json title,body,labels,comments
If the issue mentions a specific function:
If no labels exist, run /issue-label {number}.
gh issue list --repo toss/es-toolkit --state all --search "{function name}" --limit 10 --json number,title,state,labels
Group by:
### Issue #{number} — {title}
**Label**: {existing or newly applied}
**Context**: {what the function currently does, relevant code snippet}
**Analysis**: {is the request valid? design principle alignment?}
**Duplicates**: {similar issues if any}
**Action**: {label applied / needs discussion / close as wontfix / link to existing PR}
## Issue Review — {date}
| # | Title | Label | Duplicate? | Action |
|---|-------|-------|------------|--------|
- {N} issues reviewed
- {N} newly labeled
- {N} potential duplicates
- {N} actionable bugs
- {N} feature requests