fix-github-issue
Workflow for analyzing and fixing GitHub issues. Use when given an issue number to investigate and resolve.
Найдите подходящую возможность для вашего агента.
Workflow for analyzing and fixing GitHub issues. Use when given an issue number to investigate and resolve.
Combined workflow for ending an AI collaboration session. Runs reflect to capture learnings, consolidates memories, and summarizes session work. Use before ending any work session to preserve context.
Follow consistent project structure, version control practices, environment configuration, code review processes, and development conventions across the entire application. Use this skill when organizing project files and directories, when writing commit messages or creating pull requests, when managing environment variables and configuration, when participating in code reviews, when defining testing requirements, when using feature flags, when maintaining changelogs, when documenting setup instructions, or when establishing consistent development practices across the team.
Manages daily notes with M-D-YYYY format (e.g., 1-1-2026.md). Use when the user asks to view recent notes, create daily notes, read today's notes, summarize the week, or references @notes/ or dates. Can fetch last 7 days of notes.
Todoist data retrieval for Obsidian using todorust CLI. Fetch tasks and projects in ready-to-use Markdown formats. Use when skills need to: (1) Get completed tasks for daily/weekly reports, (2) Query by project, date, or filters, (3) Generate checklists or structured reports, (4) Integrate Todoist data into Obsidian notes
gh CLIでGitHub Issueを作成するスキル。現在の動作/期待する動作/再現手順/環境情報などの最小入力から、AIが作業可能な構造化Issue(調査・修正・検証の手順と受け入れ条件付き)を作成する。Codex/Claude/Gemini/Cursorで共通化したIssue作成を行うときに使用する。
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.
🛡️ Comprehensive security management for festivals including crowd control, threat assessment, emergency response, and staff coordination.
Review and score engineering specs against a quality rubric. Use when evaluating a spec draft before implementation to ensure it meets quality standards and identifies potential issues.
Create ATOMIC implementation plan for a single frontend task. Each step has exact code and verification command. IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /frontend.plan command - User explicitly asks for "atomic steps", "step-by-step plan with verification" - Have a specific task from docs/reference/frontend/tasks/ and need implementation steps - Need granular steps: Setup (create files) → Implementation (write code) → Test (verify) → Commit DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: Present plan to user (not saved to file), each step includes Files, Action, and Verify command.
Systematic PRD-driven software development workflow for Claude Code. Use when the user wants to (1) Import/parse feature bundles into draft PRDs with dependency analysis, (2) Create comprehensive Product Requirements Documents from feature descriptions, (2b) Extend existing PRDs with new requirements (version increment), (3) Break down PRDs into structured task lists with dependencies and test plans, (4) Systematically execute task lists with quality gates and verification protocols, (5) Audit test coverage and correctness against specifications, (6) Generate comprehensive PRD status reports showing completion states and progress tracking, or build complete applications from requirements through to tested implementation following enterprise-grade practices.
Systematic planning and execution of system migrations including database migrations, platform changes, and technology stack transitions.
Apply Elon Musk-inspired system design thinking for research, engineering, and business workflows: rigorously challenge requirements, delete steps, simplify/optimize what remains, accelerate iteration, then automate. Use when designing or revising systems, processes, or products that need lean, high-velocity execution.
Updates skills during project work according to their contracts. Adds references, improves explanations, and refines examples while respecting skill boundaries. Use when discovering patterns, encountering edge cases, or finding better ways to explain skill concepts. Works with skills that have Skill Contracts defined by skill-contract-generator.
AI agent that analyzes operational signals (metrics, logs, traces, alerts, SLO/SLI reports) from observability platforms (Prometheus, Datadog, New Relic, CloudWatch, Grafana, Elastic) and produces practical, risk-aware triage and recommendations. Use when reviewing system health, investigating performance issues, analyzing monitoring data, evaluating service reliability, or providing SRE analysis of operational metrics. Distinguishes between critical issues requiring action, items needing investigation, and informational observations requiring no action.
Use when processing Todoist inbox items, daily briefing tasks, or items tagged for review. Provides Eisenhower matrix classification and next action recommendations.
Plan and review requirements with discovery/decision gating and approval. Use when requirements are unclear for a feature or refactor.
Best practices for running GitHub Actions ARC runners on Rackspace Spot Kubernetes. Covers spot instance management, preemption handling, cost optimization, and resilience strategies. Activates on "rackspace spot", "spot instances", "preemption", "cost optimization", or "spot interruption".
Complete Jira Cloud REST API documentation for v2 and v3 endpoints. Use when working with Jira APIs, making Jira API calls, troubleshooting Jira integrations, or needing endpoint details. DO NOT use for general Jira usage questions or Jira web UI help.