linear-issue
Creating Linear Issues
Single-pass workflow: gather context, search existing issues, infer fields informed by what's already filed, create issue.
Workflow
1. CONTEXT → Gather signals: args, conversation, directory, git branch
2. SEARCH → list_issues broadly to find duplicates, related issues, and inform inference
3. TEAMS → list_teams to get available teams (informed by search results)
4. INFER → Determine title, description, team, priority, status, labels, project, links, relationships
5. CREATE → create_issue with inferred fields + relationships
6. REPORT → Display created issue summary
Step 1: CONTEXT
More from reviewstage/stage-cli
stage-chapters
Generate Stage chapters for the current local git branch and open them in a browser for review.
121fixing-ci
Use when CI is failing on a branch and you need to diagnose failures from GitHub, fix them locally with iterative verification, and re-push clean commits.
1trade-off
Use at any stage — planning, before implementing, or reviewing code that's already written — to surface high-level trade-offs that could significantly simplify the work. Scans two layers in strict priority order. First, user-facing behavior (features, flows, states, settings, notifications, undo, real-time, bulk ops) — cutting a behavior removes the architecture and code behind it. Second, architectural design (queues, caches, background jobs, new packages, new tables, new services, streaming, real-time infra) — cutting an architectural piece removes whole categories of implementation. Stops there; code-level simplification is outside scope. Proactively invoke whenever the scope of a task looks like it could grow, whenever you catch yourself about to add a queue, cache, new package, new table, new service, or behavior that wasn't explicitly requested, or when looking back at a recent diff that feels larger than the task warranted.
1deslop-ui
Use when building or reviewing UI components, pages, or layouts to ensure premium, intentional design that never looks vibe coded
1quality-review
Use when reviewing code changes against AGENTS.md implementation quality standards, or when asked to do an implementation quality review
1iterate-pr
Use when a PR is open and the user wants to autonomously monitor and fix PR review comments, CI failures, and rebase conflicts on a recurring loop, or when asked to babysit/iterate on a PR
1