ワンクリックで
linear-cycles
Manage Linear sprint cycles - list, create, update, delete, complete. Use when managing cycles.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Manage Linear sprint cycles - list, create, update, delete, complete. Use when managing cycles.
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-cycles |
| description | Manage Linear sprint cycles - list, create, update, delete, complete. Use when managing cycles. |
# List cycles
linear-cli c list -t ENG # Team cycles
linear-cli c list -t ENG --output json
# Current cycle
linear-cli c current -t ENG
linear-cli c current -t ENG --output json
# Create cycle
linear-cli c create -t ENG --name "Sprint 5"
linear-cli c create -t ENG --name "Sprint 5" --starts-at 2024-01-01 --ends-at 2024-01-14
# Get cycle details
linear-cli c get CYCLE_ID
# Update cycle
linear-cli c update CYCLE_ID --name "Sprint 5b"
linear-cli c update CYCLE_ID --description "Updated goals" --dry-run
# Complete a cycle
linear-cli c complete CYCLE_ID
# Delete cycle
linear-cli c delete CYCLE_ID --force
| Flag | Purpose |
|---|---|
--output json | JSON output |
--compact | No formatting |
--dry-run | Preview without updating |
--force | Skip delete confirmation |