issue-review
Review recent issues with labeling, context analysis, and duplicate detection
- Installs
- 188
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/toss/es-toolkit --skill issue-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads issue-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Issue Review
Fetch recent issues, label unlabeled ones with context, detect duplicates.
Input
$ARGUMENTS — Number of issues (default: 10)
Examples:
/issue-review— 10 most recent open issues/issue-review 20— 20 issues
Workflow
1. Fetch recent issues
gh issue list --repo toss/es-toolkit --state open --limit {count} --json number,title,author,labels,createdAt
2. Deep review per issue
For each issue:
a. Read issue content
gh issue view {number} --repo toss/es-toolkit --json title,body,labels,comments
b. Read related source code
If the issue mentions a specific function:
- Read the function source to understand current behavior
- Read existing tests to see what's covered
- Check if there's already a compat variant
c. Provide context
- Bug reports: Is the reported behavior actually a bug? Or is it by design? Does lodash behave differently?
- Feature requests: Does this align with design principles? Is it replaceable by modern JS? Is it TC39 Stage 3+?
- Type issues: Read the current type signature, assess the proposed change
- Docs: Check what's currently documented vs what's being requested
d. Label if unlabeled
If no labels exist, run /issue-label {number}.
3. Detect duplicates
gh issue list --repo toss/es-toolkit --state all --search "{function name}" --limit 10 --json number,title,state,labels
Group by:
- Same function name in title
- Similar error descriptions
- Same feature being requested
4. Report per issue
### 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}
5. Summary
## Issue Review — {date}
| # | Title | Label | Duplicate? | Action |
|---|-------|-------|------------|--------|
- {N} issues reviewed
- {N} newly labeled
- {N} potential duplicates
- {N} actionable bugs
- {N} feature requests
FAQ
What does the issue-review skill do?
Review recent issues with labeling, context analysis, and duplicate detection
How do I install issue-review?
Run npx skills add https://github.com/toss/es-toolkit --skill issue-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/issue-review/ (personal) or .claude/skills/issue-review/ (project).
Which AI agents can use issue-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is issue-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains issue-review?
It is published by toss in toss/es-toolkit. It has 188 recorded installs.
More from toss/es-toolkit
recommend
toss/es-toolkit
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.
guide
toss/es-toolkit
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.
migrate
toss/es-toolkit
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.
compat-review
toss/es-toolkit
Verify compat PR claims by running lodash vs es-toolkit/compat at runtime
pr-review
toss/es-toolkit
Review recent PRs with deep context and label-specific checks
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.