ReddRadar
Agent skill
linear
Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says 'linear', 'linear issue', 'link linear', (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.
Install this agent skill to your Project
npx add-skill https://github.com/lobehub/lobehub/tree/canary/.agents/skills/linear
SKILL.md
Linear Issue Management
Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.
⚠️ CRITICAL: PR Creation with Linear Issues
When creating a PR that references Linear issues (LOBE-xxx), you MUST:
- Create the PR with magic keywords (
Fixes LOBE-xxx) - IMMEDIATELY after PR creation, add completion comments to ALL referenced Linear issues
- Do NOT consider the task complete until Linear comments are added
This is NON-NEGOTIABLE. Skipping Linear comments is a workflow violation.
Workflow
- Retrieve issue details before starting:
mcp__linear-server__get_issue - Check for sub-issues: Use
mcp__linear-server__list_issueswithparentIdfilter - Update issue status when completing:
mcp__linear-server__update_issue - Add completion comment (REQUIRED):
mcp__linear-server__create_comment
Creating Issues
When creating issues with mcp__linear-server__create_issue, MUST add the claude code label.
Completion Comment Format
Every completed issue MUST have a comment summarizing work done:
## Changes Summary
- **Feature**: Brief description of what was implemented
- **Files Changed**: List key files modified
- **PR**: #xxx or PR URL
### Key Changes
- Change 1
- Change 2
- ...
This is critical for:
- Team visibility
- Code review context
- Future reference
PR Association (REQUIRED)
When creating PRs for Linear issues, include magic keywords in PR body:
Fixes LOBE-123Closes LOBE-123Resolves LOBE-123
Per-Issue Completion Rule
When working on multiple issues, update EACH issue IMMEDIATELY after completing it:
- Complete implementation
- Run
bun run type-check - Run related tests
- Create PR if needed
- Update status to "In Review" (NOT "Done")
- Add completion comment immediately
- Move to next issue
Note: Status → "In Review" when PR created. "Done" only after PR merged.
❌ Wrong: Complete all → Create PR → Forget Linear comments
✅ Correct: Complete → Create PR → Add Linear comments → Task done
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
lobehub/lobehub
task
lobehub/lobehub
i18n
Internationalization guide using react-i18next. Use when adding translations, creating i18n keys, or working with localized text in React components (.tsx files). Triggers on translation tasks, locale management, or i18n implementation.
lobehub/lobehub
data-fetching
Data fetching architecture guide using Service layer + Zustand Store + SWR. Use when implementing data fetching, creating services, working with store hooks, or migrating from useEffect. Triggers on data loading, API calls, service creation, or store data fetching tasks.
lobehub/lobehub
recent-data
Guide for using Recent Data (topics, resources, pages). Use when working with recently accessed items, implementing recent lists, or accessing session store recent data. Triggers on recent data usage or implementation tasks.
lobehub/lobehub
hotkey
Guide for adding keyboard shortcuts. Use when implementing new hotkeys, registering shortcuts, or working with keyboard interactions. Triggers on hotkey implementation or keyboard shortcut tasks.
lobehub/lobehub
debug
Debug package usage guide. Use when adding debug logging, understanding log namespaces, or implementing debugging features. Triggers on debug logging requests or logging implementation.
Didn't find tool you were looking for?