linear-triage
Manage Linear projects — triage boards, create issues and epics, enforce labels and metadata, audit dependencies. Use when user wants to triage issues, create/review tickets, clean up a board, manage labels/priorities/milestones, or write epics with sub-issue decomposition.
What this skill does
# Linear Triage Manage and triage issues in Linear using `mcp__claude_ai_Linear__*` MCP tools. All mutations follow **prepare → confirm → execute**: present proposed changes, wait for approval, then apply. ## Reference docs - [TRIAGE.md](TRIAGE.md) — board-level triage, health dashboard, batch operations - [ISSUE-WRITING.md](ISSUE-WRITING.md) — Why/What/How template, quality scoring, anti-patterns - [EPIC-WRITING.md](EPIC-WRITING.md) — epic structure, decomposition, sub-issue boundaries - [LABELS.md](LABELS.md) — label taxonomy and enforcement rules ## Core principles 1. **Every issue earns its place.** No Why, no concrete What, no testable acceptance criteria → flag it. 2. **Structure over volume.** A 2000-word wall of text is noise. Why/What/How with clear sections beats prose dumps. 3. **Metadata is the filtering API.** Missing labels, priorities, or milestones make the board unqueryable. 4. **Lock the contract, free the implementation.** Issues define outcomes and boundaries. The implementer decides internal code structure. 5. **Prepare, confirm, execute.** Never mutate without showing the user exactly what will change. ## Invocation The user invokes `/linear-triage` then describes what they want. **Triage requests** → follow [TRIAGE.md](TRIAGE.md): - "Triage the SDK project" / "What needs attention?" - "Review SDK-42" / "Flag issues missing labels" - "Check dependencies on the v0.12 milestone" **Issue creation** → follow [ISSUE-WRITING.md](ISSUE-WRITING.md): - "Create a ticket for X" / "Write up an issue for the auth bug" **Epic creation** → follow [EPIC-WRITING.md](EPIC-WRITING.md): - "Create an epic for the credential refactor" - "Decompose this work into sub-issues" **Label/metadata questions** → follow [LABELS.md](LABELS.md): - "What label should this get?" / "Fix all missing labels" ## Workflow: Create issue 1. Clarify with the user: what problem, what outcome, what's out of scope. 2. Draft the issue using the Why/What/How template from [ISSUE-WRITING.md](ISSUE-WRITING.md). 3. Score against the quality checklist (must score ≥ 7 for `ready`). 4. Apply metadata: priority, category label, milestone, assignee. 5. Present the full issue for confirmation before creating via `save_issue`. ## Workflow: Create epic 1. Clarify: what problem, what "done" looks like, what's NOT in scope. 2. Write the epic using the 6-section structure from [EPIC-WRITING.md](EPIC-WRITING.md). 3. Decompose into sub-issues (vertical slices, risk-ordered, 1–5 days each). 4. Write each sub-issue using Why/What/How from [ISSUE-WRITING.md](ISSUE-WRITING.md). 5. Score epic ≥ 7. Apply `epic` label + category label, priority, milestone. 6. Present epic + sub-issues for confirmation before creating. ## Workflow: Triage Follow [TRIAGE.md](TRIAGE.md) for board-level or single-issue triage. ## Comments When posting triage comments to Linear: ``` **Triage note** (generated by AI) [content] ```
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.