菜单
Complete a Linear task by checking out its branch, scoping session changes, and preparing a commit. Use when the user says "complete [ISSUE-ID]", "branch for [ISSUE-ID]", or after finishing work on a Linear task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Debug and repair code using minimal, reviewable patches instead of full-file rewrites. Use this whenever the user is fixing a bug, iterating on failing tests, asks for a surgical code change, wants a minimal diff, or is in a tight debug loop where output size and token cost matter. Prefer this even if the user does not explicitly say "patch."
Build or use a tight automated test-fix loop that repairs one failing test at a time with minimal patches and narrow context. Use whenever the user wants a repair harness, constrained bug-fixing loop, failing-test repair workflow, or a prompt that turns the model into a surgical fix engine instead of a general coding assistant.
Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)
Reduce cognitive load when implementing or refactoring code for readability.
Use Conventional Commits when creating reviewing or fixing commit messages.
Audit and refactor React UI components to match DataConnect UI implementation rules (Text component, tokens, Tailwind, naming) and Vercel React/composition guidance. Use when the user asks for a UI audit, React audit, composition review, or to fix UI implementation issues in components.
| name | linear-task-completion |
| description | Complete a Linear task by checking out its branch, scoping session changes, and preparing a commit. Use when the user says "complete [ISSUE-ID]", "branch for [ISSUE-ID]", or after finishing work on a Linear task. |
After finishing work on a Linear task, execute this workflow.
Use the MCP Linear tool via CallMcpTool after reading its schema in
/Users/callumflack/.cursor/projects/Users-callumflack-Repos-vana-vana-app/mcps/user-Linear/tools/.
Extract gitBranchName and the issue ID from the response.
git checkout -b <gitBranchName>
If gitBranchName is missing, follow .cursor/rules/linear-task-creation.mdc
to create and checkout a branch name that includes the issue ID.
Important: Track which files were actually modified during this session.
git status to see unstaged changesgit add <specific-files-from-step-3>
Commit message format:
ISSUE_ID: <commit message>
Do NOT commit unless explicitly asked.
If the user asks for a commit message only, provide the message and stop.
Commit/branch conventions: .cursor/rules/linear-task-creation.mdc