Menu
Sprint planning and analytics - status, progress, burndown, velocity, carry-over. Use when managing sprints.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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-sprint |
| description | Sprint planning and analytics - status, progress, burndown, velocity, carry-over. Use when managing sprints. |
# Current sprint status
linear-cli sp status -t ENG
# Sprint progress (completion bar)
linear-cli sp progress -t ENG
# Plan next sprint (view planned issues)
linear-cli sp plan -t ENG
# Carry over incomplete issues to next cycle
linear-cli sp carry-over -t ENG --force
# ASCII burndown chart
linear-cli sp burndown -t ENG
# Velocity across recent sprints
linear-cli sp velocity -t ENG
linear-cli sp velocity -t ENG --cycles 10 # Last 10 sprints
linear-cli sp velocity -t ENG --output json
| Command | Purpose |
|---|---|
status | Current sprint overview |
progress | Visual completion bar |
plan | Next cycle's planned issues |
carry-over | Move incomplete to next cycle |
burndown | ASCII burndown chart |
velocity | Sprint velocity + trend analysis |
| Flag | Purpose |
|---|---|
-t TEAM | Team key (required) |
--cycles N | Number of past cycles for velocity |
--force | Skip carry-over confirmation |
--output json | JSON output |
0=Success, 1=Error, 2=Not found, 3=Auth error