一键导入
linear-pr
Create GitHub PRs linked to Linear issues. Use when creating pull requests, pushing code for review, or linking PRs to Linear issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create GitHub PRs linked to Linear issues. Use when creating pull requests, pushing code for review, or linking PRs to Linear issues.
用 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-pr |
| description | Create GitHub PRs linked to Linear issues. Use when creating pull requests, pushing code for review, or linking PRs to Linear issues. |
Create GitHub pull requests linked to Linear issues using linear-cli.
# Create PR linked to Linear issue
linear-cli g pr LIN-123
# Draft PR
linear-cli g pr LIN-123 --draft
# Specify base branch
linear-cli g pr LIN-123 --base main
# Open in browser after creation
linear-cli g pr LIN-123 --web
# Create and checkout branch for issue
linear-cli g checkout LIN-123
# Custom branch name
linear-cli g checkout LIN-123 -b my-custom-branch
# Just show branch name (don't create)
linear-cli g branch LIN-123
# Create branch without checkout
linear-cli g create LIN-123
# 1. Start work (assigns, sets In Progress, creates branch)
linear-cli i start LIN-123 --checkout
# 2. Make changes and commit
git add . && git commit -m "Fix the bug"
# 3. Create PR
linear-cli g pr LIN-123
# 4. Mark done
linear-cli i update LIN-123 -s Done
# Get issue from current git branch
linear-cli context
linear-cli context --output json
--draft for work-in-progressusername/lin-123-issue-titlegh CLI for GitHub operations