2.8K skills · sorted by relevance
Turn implementation plan phases into GitHub Issues with structured titles, descriptions, and labels. Check existing issues first, then create or update one issue per phase using feature or chore templates where available.
Review Ant Design GitHub issues and prepare responses, labels, and closure recommendations. It distinguishes bugs from feature requests, checks bot answers, and presents a complete plan for approval before making changes.
Compare specification requirements with the codebase and create GitHub issues for unmet requirements. Check existing issues for duplicates, then include requirement IDs, implementation guidance, context, and acceptance criteria in each new issue.
repo の root に issues/ を作り、dotfiles の issues/README.md を持ち込んで issue 運用を始める。commit するかはユーザーに聞く。「issue運用を始めて」「issuesディレクトリを作って」「start-issues-ops」で発火。
The English summary is being prepared. Showing the original description.
Audit GitHub issues to find open work outside a masterplan, distinguishing missing parents from missing plan ancestors. Preview or apply removal of closed issues from the hierarchy while keeping their open children connected to the plan.
Organize GitHub issues using parent and child relationships and links showing which tasks must finish first. Use gh CLI to create, change, remove, and inspect relationships, including links across repositories.
Review Azure infrastructure code and deployed resources against five Well-Architected Framework pillars. Identify configuration drift, classify risks, and produce remediation guidance and an architecture diagram, with GitHub issues created after user approval.
Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.
Organize open GitHub issues and pull requests using the gh CLI, GitHub's command-line tool. Identifies resolved issues and pending fixes, estimates priorities and change sizes locally, and proposes closures, links, reviews, or merges for approval.
Find and select Squad operations through a categorized menu, from managing an AI team and GitHub issues to choosing models and reviewing activity. The skill collects required options and routes requests to CLI commands or the coordinator agent.
Organize open GitHub issues by category, risk, linked pull requests, duplicate candidates, and inactivity. Optionally analyze selected issues in depth, draft responses, and apply approved comments, labels, or closures to keep the backlog actionable.
Assigns a specified set of GitHub issues to a milestone, owners, or both. Checks that each target is an open issue, applies changes individually, and reports results with verification of milestone counts and selected issue details.
Create and update GitHub issues for bugs, feature requests, and tasks. Organize owners, labels, dates, and priorities, connect related work, and track dependencies and project progress through MCP tools and the GitHub API.
Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.
Collect new feedback from configured Slack and GitHub Issues sources, acknowledge receipt, analyze recordings, and verify claimed fixes against the default branch. Combine unresolved items into a rolling plan ready for the lfg workflow.
Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.
Plan task handoffs between agents on different machines using Git to share YAML task and result files. This implementation specification describes validation, execution limits, result reporting, and GitHub Issues as an additional route for urgent requests.
Turn GitHub issues into pull requests, proposed code changes ready for review. Filter issues, avoid duplicate work, and assign background agents to implement fixes, run tests, and optionally address review comments.
Work with Jira issues through Orca's command-line interface. Search issues, move them through workflow states, create follow-up issues, and record completion with a PR or MR link and a comment using guidance matched to the installed Orca version.
Create and organize GitHub issues with templates, labels, assignees, and milestones. Coordinate multiple agents to track progress, post updates, and manage related issues across repositories as part of a shared project workflow.
Review open GitHub issues for herdr and organize them into a concise Markdown table. Each row shows urgency, a recommended action, issue age, reactions, and a short reason to help decide what needs attention.
Review GitHub issue discussions and code on the target branch to confirm a fix has landed, then close resolved issues with evidence, contributor credit, and an invitation to reopen if the problem returns.
Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.
Turn validated Codex Security findings into tracked issues in Linear, Jira, or GitHub, or draft GitHub security advisories. Checks duplicates and visibility, previews exact changes for approval, and verifies results after writing.