Loading...
Loading...
Found 75 Skills
Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.
Agile methodologies, issue tracking, and team collaboration tools
**프로젝트 관리 트래커**: WBS(업무분류체계), 간트차트, 진행률 대시보드, 이슈 트래커를 생성합니다. 한국 기업 실무에 맞는 프로젝트 관리 양식과 보고 체계를 포함합니다. - MANDATORY TRIGGERS: 프로젝트, WBS, 간트차트, 일정 관리, 프로젝트 관리, 마일스톤, 이슈 트래커, 진행률, 타임라인, PM
This skill should be used when a user wants to decompose an Epic into its complete set of Features all at once, invoked automatically after write-epic completes, or triggered by phrases like "create all features for this epic", "walk me through all the features", "let's break down this epic", or "plan the features for epic
Instructions for using the Linear CLI to manage issues, projects, teams, and more in Linear
Accelerate software development with Linear project management and MCP server integration. Master issue tracking, project workflows, and development automation for frontend, full-stack, and mobile applications. Includes comprehensive MCP tool usage, workflow patterns, and development best practices.
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.
Expertise in structured Git commit workflow with Chinese team conventions. Use this skill when the user asks to "commit", "提交", "stage", "暂存", "show status", "git status", or any variant related to managing git changes. The user does NOT need to explicitly mention "git-commit-workflow" - ANY request to commit changes or manage git state should automatically trigger this skill. Handles automatic commit message generation with PMS and GitHub Issue tracking, following strict 80-character line limits.
Discover and apply labels to GitHub PRs and issues using the gh CLI. Use when you need to list available labels, add or remove labels on pull requests or issues, or create new labels for a repository.
Fetch and analyze Sentry issues, events, transactions, and logs. Helps agents debug errors, find root causes, and understand what happened at specific times.
Drafts initial ticket requirements by asking targeted clarifying questions and producing a structured ticket with Title, Body, and Acceptance Criteria. Use when a user has a request that needs to be converted into a clear tracker-ready ticket without codebase or architecture analysis.
Review current branch for blindspots; fix now / needs spec / create issues.