Menü
Import issues from CSV or JSON files. Use when bulk-creating issues from external data.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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-import |
| description | Import issues from CSV or JSON files. Use when bulk-creating issues from external data. |
# Import from CSV
linear-cli im csv issues.csv -t ENG
# Preview without creating (dry run)
linear-cli im csv issues.csv -t ENG --dry-run
# Import from JSON
linear-cli im json issues.json -t ENG
# JSON round-trip (export then re-import)
linear-cli exp json -t ENG -f backup.json
linear-cli im json backup.json -t ENG
CSV files need a header row. Supported columns: title, description, priority, status, assignee, labels, estimate, dueDate.
Status, assignee, and labels are resolved by name automatically.
JSON files should be an array of issue objects matching the export format.
| Flag | Purpose |
|---|---|
-t TEAM | Target team (required) |
--dry-run | Preview without creating |
--output json | JSON output |
0=Success, 1=Error, 2=Not found, 3=Auth error