원클릭으로
linear-list
List and get Linear issues. Use when viewing issues, checking status, or fetching issue details.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
List and get Linear issues. Use when viewing issues, checking status, or fetching issue details.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Diagnose Azedarach command latency and daemon/TUI performance with OpenTelemetry traces exported to a local Jaeger backend. Use when investigating slow `az` commands, TUI stalls, daemon RPC latency, missing spans, local Jaeger setup, or trace-driven performance regressions in this repository.
Review and integrate Azedarach issues that are in_review. Use when Codex is asked to run a reviewer/integrator session, sweep active issues that are ready for review, inspect worker evidence and diffs, return actionable findings to live or paused issue sessions, close accepted work, or get in_review issues integrated.
Review, consolidate, test, and harden Azedarach SQLite migrations before integration. Use for any migration, schema ensure/repair logic, trigger or index change, persistence-authority change, migration failure, or pre-merge review of a branch containing database changes. Also use when validating upgrades against real root-user or registered project databases.
Run an iterative code review and fix cycle until findings stabilize. Use when the user asks Codex to review code, review and fix, loop review/fix, address review findings, harden a change before handoff, or keep reviewing until repeated passes find no new actionable issues. Also use proactively before Codex declares coding work done, marks an issue in_review, says a change is ready, or hands off implementation that modified code, tests, build scripts, migrations, config, or developer tooling.
Go Testing Skill
Build and review production-grade Go logging and observability with `log/slog` and OpenTelemetry. Use when adding or refactoring logs, instrumenting request paths, defining event schemas, reducing log cost/cardinality, enforcing redaction/PII policy, correlating logs with traces, or reviewing Go services for observability gaps.
| name | linear-list |
| description | List and get Linear issues. Use when viewing issues, checking status, or fetching issue details. |
# List issues
linear-cli i list # All
linear-cli i list -t ENG # By team
linear-cli i list -s "In Progress" # By status
linear-cli i list --assignee me # My issues
# Get issue(s)
linear-cli i get LIN-123
linear-cli i get LIN-1 LIN-2 LIN-3 # Multiple
# Agent-optimized
linear-cli i list --output json --compact --fields identifier,title,state.name
| Flag | Purpose |
|---|---|
--output json | JSON output |
--compact | No formatting |
--fields a,b | Select fields |
--sort field | Sort results |
0=Success, 1=Error, 2=Not found, 3=Auth error