mirror of https://github.com/lobehub/lobe-chat.git synced 2026-06-13 19:20:04 +00:00

Files

T

Innei 346fc4617e ♻️ refactor: migrate AI Rules to Claude Code Skills (#11737 )

♻️ refactor: migrate AI Rules to Claude Code Skills system

Migrate all AI Rules from .cursor/rules/ to .agents/skills/ directory:
- Move 23 skills to .agents/skills/ (main directory)
- Update symlinks: .claude/skills, .cursor/skills, .codex/skills
- Create project-overview skill from project documentation
- Add references/ subdirectories for complex skills
- Remove LobeChat references from skill descriptions
- Delete obsolete .cursor/rules/ and .claude/commands/prompts/ directories

Skills structure enables better portability and maintainability across AI tools.

2026-01-23 22:30:18 +08:00

1.7 KiB

Raw Blame History

name, description

name	description
linear	Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.

Linear Issue Management

Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.

Workflow

Retrieve issue details before starting: mcp__linear-server__get_issue
Check for sub-issues: Use mcp__linear-server__list_issues with parentId filter
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 (REQUIRED)

Every completed issue MUST have a comment summarizing work done. 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-123
Closes LOBE-123
Resolves 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
Move to next issue

Note: Status → "In Review" when PR created. "Done" only after PR merged.

❌ Wrong: Complete all → Update all statuses → Add all comments

✅ Correct: Complete A → Update A → Comment A → Complete B → ...

1.7 KiB Raw Blame History