بنقرة واحدة
linear-create
Create Linear issues. Use when creating bugs, tasks, or feature requests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create Linear issues. Use when creating bugs, tasks, or feature requests.
التثبيت باستخدام 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-create |
| description | Create Linear issues. Use when creating bugs, tasks, or feature requests. |
# Basic
linear-cli i create "Title" -t TEAM
# With options
linear-cli i create "Bug" -t ENG -p 1 # Priority (1=urgent)
linear-cli i create "Task" -t ENG -a me # Assign to self
linear-cli i create "Fix" -t ENG -l bug # With label
linear-cli i create "Due" -t ENG --due +3d # Due date
# Agent patterns
linear-cli i create "Bug" -t ENG --id-only # Return ID only
linear-cli i create "Test" -t ENG --dry-run # Preview
cat desc.md | linear-cli i create "Title" -t ENG -d -
1=Urgent, 2=High, 3=Normal, 4=Low
today, tomorrow, +3d, +2w, monday, eow, eom
| Flag | Purpose |
|---|---|
--id-only | Return ID only |
--dry-run | Preview |
--quiet | No output |