بنقرة واحدة
linear-projects
Manage Linear projects - full CRUD with labels, members, archive. Use when managing projects.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Manage Linear projects - full CRUD with labels, members, archive. Use when managing projects.
التثبيت باستخدام 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-projects |
| description | Manage Linear projects - full CRUD with labels, members, archive. Use when managing projects. |
# List projects
linear-cli p list # All projects
linear-cli p list --archived # Include archived
linear-cli p list --view "Active" # Apply saved view
# Get project
linear-cli p get PROJECT_ID
linear-cli p open PROJECT_ID # Open in browser
# Create project (full API fields)
linear-cli p create "Q1 Roadmap" -t ENG
linear-cli p create "Feature" -t ENG --icon "🚀" --priority 1 \
--start-date 2025-01-01 --target-date 2025-03-31 \
--lead USER_ID --status planned --content "Project description"
# Update project
linear-cli p update PROJECT_ID --name "New Name" --status completed
linear-cli p update PROJECT_ID --lead USER_ID --priority 2
# Archive/unarchive
linear-cli p archive PROJECT_ID
linear-cli p unarchive PROJECT_ID
# Labels
linear-cli p add-labels PROJECT_ID -l label1 -l label2
linear-cli p remove-labels PROJECT_ID -l label1
linear-cli p set-labels PROJECT_ID -l label1 -l label2
# Members
linear-cli p members PROJECT_ID
# Delete
linear-cli p delete PROJECT_ID --force
| Flag | Purpose |
|---|---|
--icon EMOJI | Project icon |
--priority N | Priority (1=urgent, 4=low) |
--start-date DATE | Start date |
--target-date DATE | Target date |
--lead USER | Project lead |
--status STATE | Project status |
--id-only | Return ID only |
--output json | JSON output |