メニュー
Manage project milestones - create, update, track target dates. Use when planning project deliverables.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | linear-milestones |
| description | Manage project milestones - create, update, track target dates. Use when planning project deliverables. |
# List milestones for a project
linear-cli ms list -p "My Project"
linear-cli ms list -p "My Project" --output json
# Get milestone details
linear-cli ms get MILESTONE_ID
# Create a milestone
linear-cli ms create "Beta Release" -p "My Project"
linear-cli ms create "GA" -p PROJ --target-date 2025-06-01
# Update a milestone
linear-cli ms update MILESTONE_ID --target-date +2w
linear-cli ms update MILESTONE_ID --name "Renamed"
# Delete a milestone
linear-cli ms delete MILESTONE_ID --force
| Flag | Purpose |
|---|---|
-p PROJECT | Project name/ID |
--target-date DATE | Target date (YYYY-MM-DD or +Nw) |
--name NAME | Milestone name |
--output json | JSON output |
0=Success, 1=Error, 2=Not found, 3=Auth error
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.