Essential command-line tools and system utilities.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
Creates GitHub issues to capture work that needs to be done. Records intent with context about the codebase, not implementation plans. Use when the user wants to track work, create a ticket, log a task, or says "we want to do X" or "we need to X".
Code Reviewer persona for technical code analysis. ACTIVATE when messages contain review code, analyze code, code quality, best practices, refactor, improve code, check code, code review, look at code, feedback on code, or constructive feedback requests.
Use when completing work on a task or feature. Prompts for code review before finishing. ALWAYS invoke this skill before saying work is done.
Analyzes issues from any tracker (Linear, GitHub, Jira), explores the codebase for context, and creates implementation plan files. Use when starting work on an issue. Takes issue URL/ID as input. Invokes implementation-plan-writer to create the plan file.
Create, manage, and optimize email campaigns for Laguna Beach Tennis Academy using ActiveCampaign. Use when Claude needs to: (1) Create email campaigns for program launches, camps, or events, (2) Build automation workflows and nurture sequences, (3) Manage contact lists and segmentation, (4) Design luxury-branded email templates following LBTA brand guidelines, (5) Set up triggered emails for registrations or trials, (6) Analyze campaign performance or optimize email strategy.
Complete plan execution with git workflow and PR management
Task management and tracking system using markdown files. Create and maintain task boards to track project progress, status, and priorities. Use when starting new projects, refactoring code, or managing complex multi-step tasks that require organized tracking.
Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, non-functional requirements, SRS, requirement analysis, specification, acceptance criteria, requirement validation Use when: User requests involve requirements analyst tasks.
Execute systematic feature development using EPIC methodology (Explore, Research, Plan, Validate, Implement, Review, Iterate). Use when building features, implementing complex tasks, or following structured development workflows. Delegates exploration, research, planning, validation, and review to specialized agents.
Review architecture decisions and code changes against documented architecture principles. Use this skill before implementing new features or refactoring existing code to ensure compliance with layer boundaries, separation of concerns, and design patterns. Should be invoked when user requests "architecture review" or before making significant changes.
要件、設計ドキュメント、会話内容からGitHub Issueを作成する。ユーザーが計画ドキュメントからIssueを作成したい、要件をIssueに変換したい、タスクをIssueとして登録したい、または複数の関連するIssueをまとめて作成したい場合に使用。「この要件をIssueに登録」「plan.mdをIssueにして」「要件ごとにIssueを作って」などのリクエストでトリガーされる。
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
Administrative tasks, RBAC hierarchy, and business workflows.
Use this skill to propose changes via the Spec PR process. It uses the Gemini CLI to generate high-quality draft specifications and to analyze PR feedback, accelerating the spec-driven development workflow. Triggers include "create spec" or "propose change".
Load when user says "validate skill", "validate this skill", "review skill execution", "check skill", or "skill validation" at the end of executing a skill. Post-execution review workflow for validating that a skill worked correctly, documenting findings, and identifying issues.
Creates a high-level implementation plan file for issues from any tracker (Linear, GitHub, Jira) that another Claude Code instance can use as a guide. Use when the user asks to create an implementation plan file or document a feature's implementation approach.
Use when (1) creating GitHub issues from feature plans or bug reports, (2) documenting bugs found during development, (3) managing the project backlog. Creates well-structured GitHub issues with templates and labels.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Build concise session context by extracting key information from project logs (CLAUDE.md, TASK_BOARD.md, MIGRATION_LOG.md, DEBUG_LOG.md, GIT_LOG.md, SKILLS_LOG.md) to provide token-efficient project status. Use when beginning work, returning after break, or needing quick project overview without reading full files.
Create a Linear Document with technical design using Approach Mode brainstorming. Same process as /brainstorm how, outputs to Linear Document. Triggers - linear design, design to linear, technical design, architecture decision.
Create a milestone within an existing Linear project and optionally create issues from plans. Lists user's projects for selection, suggests milestone names, and can associate plan-based issues with the milestone. Use when user wants to add milestones to Linear projects.
Analyze Output SDK workflow execution traces. Use when debugging a specific workflow, examining step failures, analyzing input/output data, understanding execution flow, or when you have a workflow ID to investigate.
How Claude Code handles git commits and pull requests, including git safety protocols and best practices. Use when user asks about creating commits, making PRs, git workflows, or git safety.
