to-be-cont
Comprehensive documentation review and analysis of to-be-continuous GitLab CI/CD templates and framework architecture
Find the perfect capability for your agent.
Comprehensive documentation review and analysis of to-be-continuous GitLab CI/CD templates and framework architecture
実装状況に応じて Issue の状態を更新する。「Issue 更新」「Issue を更新」「Issue 状態変更」「Issue をクローズ」「Issue 完了」「チケットを閉じる」「Issue の進捗を更新」などで起動。コメント追加やラベル変更、クローズ処理を実行。
This skill should be used when the user asks to "generate commit message", "write commit message", "create git commit", or mentions analyzing staged changes for commits.
Generate a plain-language activity report of your GitHub work for a given date range, including commits, pull requests, reviews, issues, and comments. Use this when you need to summarize what you've accomplished on GitHub for status updates, retrospectives, or tracking your work.
MANDATORY: Use gh (GitHub) or glab (GitLab) CLI for ALL issue/task management. Unified workflow across platforms.
Commands for creating new issues and managing priority on the Guidr GitHub Projects board. Includes issue templates for features, bugs, documentation, and technical debt.
Fetches the next task from GitHub Projects for this repository. Prioritizes earlier phases when tasks are still open. Use when the user asks for the next task, what to work on, next item, or wants to pick up work from the project board.
This skill should be used when the user asks to "generate social preview", "create social image", "github social preview", "repository preview image", "og image", "social media card", "create repo image", "github card image", or needs to create an image that captures a project's spirit and purpose for social media sharing. Analyzes project files to understand intent and generates optimized SVG graphics or AI-generated images.
Adapt UI scheduling behavior dynamically based on runtime conditions and user context.
정기 회의록 GitHub Discussion에 자동 생성. Use when (1) "정기 회의록 생성해줘", (2) /create-meeting-minutes 커맨드, (3) "이번 주 회의록 만들어줘", (4) 이터레이션 기반 회의록 생성 요청.
Comprehensive guidance for writing user stories following Nimble's product development standards. Use when creating product requirements, organizing backlogs, writing user stories, documenting bugs, or creating chores for digital product development at Nimble. Covers backlog organization (modules, features, labels), user story types (features, bugs, chores), story templates, naming conventions, and estimation guidelines.
Invoke for complex multi-step tasks requiring intelligent planning and multi-agent coordination. Use when tasks need decomposition, dependency mapping, parallel/sequential/swarm/iterative execution strategies, or coordination of multiple specialized agents with quality gates and dynamic optimization.
Expert software engineering lead who translates product requirements into comprehensive engineering plans using GitHub Projects. Reviews PRDs and user stories, identifies gaps and conflicts, pushes back constructively on poor requirements, applies software engineering best practices, creates detailed technical plans with tasks and milestones, and ensures production-ready architecture. Use when translating product specs into actionable development plans, validating requirements, or designing system architecture.
Create, edit, delete, and organize GitHub Issue labels and milestones. Use for label operations, milestone management, or organizing issue taxonomy.
Use this agent when you need to conduct thorough research on a repository's structure, documentation, and patterns. This includes analyzing architecture files, examining GitHub issues for patterns, reviewing contribution guidelines, checking for templates, and searching codebases for implementation patterns. The agent excels at gathering comprehensive information about a project's conventions and best practices.\n\nExamples:\n- <example>\n Context: User wants to understand a new repository's structure and conventions before contributing.\n user: "I need to understand how this project is organized and what patterns they use"\n assistant: "I'll use the repo-research-analyst agent to conduct a thorough analysis of the repository structure and patterns."\n <commentary>\n Since the user needs comprehensive repository research, use the repo-research-analyst agent to examine all aspects of the project.\n </commentary>\n</example>\n- <example>\n Context: User is preparing to create a GitHub issue and wants to
Guide for debugging failing GitHub Actions workflows. Use this skill when debugging failing GitHub Actions workflows.