Menu
Read and parse GitHub issues; extract title, body, labels, checklists, and acceptance criteria to support triage and delegation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, or enforcing design consistency.
Making changes to the app's functionality.
Create Criterion benchmarks with proper group macros and configuration. Use when writing benchmarks, creating benchmark groups, using criterion_group! and criterion_main! macros, setting throughput, or benchmarking multiple implementations. Handles benchmark groups, throughput metrics, conditional compilation, and proper black_box usage.
Apply cognitive and perception-based UI principles from Laws of UX. Use when evaluating layout, interaction design, target size and distance, choice count, information grouping, memory load, or response time. Cites specific laws (e.g. Fitts's Law, Hick's Law) to justify design decisions or suggest improvements.
Work with async/await, futures, and asynchronous Rust code. Use when writing async functions, working with tokio or async-std, understanding futures, or implementing async traits. Handles async/await syntax, futures, executors, pinning, Send/Sync bounds, and async patterns.
Use std::hint::black_box correctly in benchmarks and tests. Use when writing benchmarks, preventing compiler optimizations, or ensuring code actually executes. Handles proper placement, when to use it, and common patterns for benchmarking.
| name | github-issues |
| description | Read and parse GitHub issues; extract title, body, labels, checklists, and acceptance criteria to support triage and delegation. |
This skill guides reading and parsing GitHub issues so task type, scope, and acceptance criteria can be extracted for triage and delegation.
gh issue view <number> --repo owner/repo to fetch an issue. Use --web to open the issue in the browser and get the URL.Ensure you have the full issue content (title, body, labels) before parsing.
bug, documentation, enhancement, testing, release, ui, accessibility.Emphasize body and labels when determining task type.
- [ ] or - [x]## Acceptance criteria, ## Requirements, ## Done whensrc/parser.rs", "QC page", "workspace persistence"). Note "whole project" if no scope is given.Use labels to suggest which subagent might handle the work (the subagent-delegation skill makes the final choice):
| Label / theme | Candidate subagent(s) |
|---|---|
bug, errors | debugger, test-runner |
documentation | documenter |
testing, ci | test-runner |
release | cargo-release |
ui, ux, accessibility | ui-ux-reviewer |
| Performance | benchmarker |
| Review / quality | code-reviewer |
| Verify / validate | verifier |
Extract these fields and pass them to the delegation step so the right subagent and a clear prompt can be chosen.