ワンクリックで
linear-project-updates
Manage project status updates - create, list, archive. Use when posting or viewing project health updates.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Manage project status updates - create, list, archive. Use when posting or viewing project health updates.
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-project-updates |
| description | Manage project status updates - create, list, archive. Use when posting or viewing project health updates. |
# List updates for a project
linear-cli pu list "My Project"
linear-cli pu list "My Project" --output json
# Get update details
linear-cli pu get UPDATE_ID
# Create a project update
linear-cli pu create "My Project" -b "On track this sprint"
linear-cli pu create "My Project" -b "Blocked on API" --health atRisk
# Update an existing update
linear-cli pu update UPDATE_ID -b "Updated status"
# Archive/unarchive
linear-cli pu archive UPDATE_ID
linear-cli pu unarchive UPDATE_ID
| Value | Meaning |
|---|---|
onTrack | Project is on track (green) |
atRisk | Project is at risk (yellow) |
offTrack | Project is off track (red) |
| Flag | Purpose |
|---|---|
-b BODY | Update body text |
--health STATUS | Health status |
--output json | JSON output |
0=Success, 1=Error, 2=Not found, 3=Auth error