git-workflow-mastery
Advanced Git workflows, branching strategies, and commit conventions
Найдите подходящую возможность для вашего агента.
Advanced Git workflows, branching strategies, and commit conventions
See the main On-Call Playbooks skill for comprehensive runbook templates and examples.
生成GOAL/SubPlan依赖DAG和关键路径分析,并执行SubPlan划分。当需要分析技术依赖、业务依赖、识别关键路径、发现并行执行机会、执行SubPlan分配时使用。基于GOAL的dependencies字段和业务逻辑分析生成Mermaid依赖图和SubPlan划分方案。
Use for ANY bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Four phases: investigate, analyze, hypothesize, implement. Ensures understanding before attempting solutions.
Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs.
Orchestrate multi-agent swarms with agentic-flow for parallel task execution, dynamic topology, and intelligent coordination. Use when scaling beyond single agents, implementing complex workflows, or building distributed AI systems.
Show details for a Beads task by id (including audit trail)
Force honest confidence assessment before claiming conclusions. Triggers on 'root cause identified', 'problem identified', 'complete clarity'. Express confidence as percentage, explain what's stopping 100%, validate assumptions before presenting.
Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)
Facilitate structured brainstorming sessions using proven frameworks for ideation and problem-solving
Integrated project management system with documentation, language initialization, and template optimization modules
Create a comprehensive specification file with deep codebase analysis. Generates detailed requirements, technical designs, and implementation logistics. The spec serves as the source of truth for related plans.
Systematic approach to choosing technologies, frameworks, and tools based on requirements, team capabilities, and long-term sustainability.
[62] VALIDATE. Final self-check before delivery. Verify goal alignment, completeness, correctness, and identify residual risks. Produces quality score (0-100) and delivery status. Use when completing any significant work, before handoff, or when you need confidence that work is ready.
Troubleshoot ARC (Actions Runner Controller) runners on Rackspace Spot Kubernetes. Diagnose stuck jobs, scaling issues, and cluster access. Activates on "runner", "ARC", "stuck job", "queued", "GitHub Actions", or "CI stuck".
Brainstorm ideas from simple features to entire projects. Use when user wants to explore an idea, brainstorm, plan something new, or think through changes. Triggers on "brainstorm", "I have an idea", "let's think through", "help me plan", or ideation requests. Creates minimal SPEC.md, then invokes interview-project for large-scope ideas (new projects, major refactors, infrastructure changes).
Create, update, and maintain clear, accurate, and well-organized technical documentation for complex codebases. This agent focuses on understanding the current state of the code and existing documentation before proposing or making changes, ensuring documentation remains up to date, discoverable, and trustworthy for developers.
Steps for creating better Github actions by gathering context on how they are used
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.
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.