Loading...
Loading...
Found 101 Skills
GitHub operations skill for gh CLI issue, label, template, and workflow management. Use when requests include: create issue, list issues, apply label, manage templates, check workflow, or gh operations.
Sync project state with Linear — detect gaps, consolidate objectives, clean up, route to next action
GitHub 审视 - Read-only GitHub triage for issues and PRs. 触发条件/Triggers: 需要分析 GitHub Issues 或 PRs、生成审查报告、或分类问题。 核心原则/Core Principles: - 只读不写/Read-only: 永不修改 GitHub 状态 - 证据支持/Evidence: 每个结论都需要 GitHub permalink 证明 - 并行分析/Parallel: 每个 Issue/PR 独立后台任务 - 报告输出/Reports: 写入临时目录，不操作 GitHub 命令/Commands: - /审视 analyze <repo> - 分析仓库所有开放 Issue 和 PR - /审视 issues <repo> - 只分析 Issues - /审视 prs <repo> - 只分析 PRs - /审视 <URL> - 分析特定 Issue 或 PR - /analyze <repo> - English command 能力/Capabilities: GitHub 数据读取、问题分类、证据收集、报告生成、后台并行处理。
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Full Jira Data Center control from the terminal. Manage issues, sprints, boards, epics, projects, users, and filters. Use --json flag for machine-readable output when parsing results programmatically.
Create a PRD from current context, then break it into tracer-bullet issues and publish everything to the project issue tracker. Use when user wants end-to-end issue creation from a plan, idea, or requirement.
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.
Sentry API via curl. Use this skill to manage error tracking, list issues, resolve errors, and monitor releases in Sentry.
Update a GitHub issue with new title, body, labels, or assignees. Use when the user wants to edit an issue, change labels, or update issue details.
Creates a new numbered issue document in docs/issue/ following the project's standard issue format, and simultaneously creates the corresponding Korean translation in docs/dev/issue/. Use this whenever starting new work — features, bug fixes, tasks, or investigations. The user may say "create an issue", "new issue", "이슈 만들어줘", or simply describe work they want to start.
Use when querying, creating, updating, or managing Linear issues, projects, teams, and initiatives. Auto-invoke when the user mentions Linear tickets, issue tracking, or task management.
Use when starting a session to find work, creating/triaging issues, or completing work and updating issue status