2.9K skills · sorted by relevance
Analyze Azure infrastructure definitions, deployed resources, usage metrics, and pricing to identify cost reductions. Rank recommendations by savings, risk, and effort, then create individual GitHub issues and a coordinating EPIC issue after user approval.
Manage Jira issues through natural language using jira CLI or Atlassian MCP, a tool connection. Search and view tickets, draft new issues, update assignments or status, and check sprints, with review and approval before changes.
Turn the latest Granola call into action items with owners, teams, due dates, and matching existing Linear issues. It uses cognee memory of calls, issues, and Gmail, then prints the results or posts them to configured Slack.
Coordinate multiple Mastra Code workers to investigate and fix GitHub issues in parallel. Keep each issue in a separate working directory, track progress in reports, review changes, and manage pull requests, reviewer feedback, and automated checks.
Manage Linear issues and projects through natural-language requests. Review priorities, create and update tickets, inspect team workloads, and organize release plans using a workflow that reads existing information before making changes.
Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.
Organize Jira issues, plan sprints, and define workflows with clear ownership and acceptance criteria. Get help writing JQL, Jira's query language, to find stalled work, review workloads, and support project reporting.
Manage Linear issues and projects through natural-language requests. Review priorities, create and update tickets, inspect team workloads, and organize release plans using a workflow that reads existing information before making changes.
Review OpenShell issues, pull requests, and failed main-branch checks, then build a local Markdown report with linked evidence and ranked recommendations. Saved progress helps resume an unfinished triage pass without changing GitHub.
Check whether OpenShell issues and pull requests fit the project, then track review feedback and automated checks. State labels show what needs attention and when a pull request is ready for maintainer approval or a merge decision.
Find Linear issues by text, assignee, or status, and read their details and comments. Prepare new issues, comments, and status changes for user approval, then return identifiers and links so results can be checked.
Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.
Audit groups of bug reports to find shared root causes, checking claims against current code and tests. Produce a cause map, prioritize fixes that remove faulty mechanisms, and document which issues have enough evidence to close.
Review Git code changes using the CodeRabbit CLI. Receive a summary of the changes and issues ordered by severity, with affected file paths, practical impact, and concrete suggestions for follow-up fixes.
Inspect production errors recorded in Sentry through read-only API access. Summarize unresolved issues, recent crashes, occurrence counts, and event details to understand what happened and when each problem was last seen.
Manage Jira issues through Atlassian MCP, a connection that lets an AI agent use Jira tools. Find tasks, create issues and subtasks, update assignees, add comments, and change status using the detected project configuration.
Turn a Seed specification into GitHub issues for team planning. The skill creates a parent issue and implementation tasks, distributes acceptance criteria across them, and links the tasks in a progress checklist.
Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues + agent:implement multi-session workflow. Argument is the parent PRD issue number.
The English summary is being prepared. Showing the original description.
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
The English summary is being prepared. Showing the original description.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
The English summary is being prepared. Showing the original description.
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
The English summary is being prepared. Showing the original description.
Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues. Not for finding problems that nobody has filed an issue for yet. Use oss-find-real-issues for that.
The English summary is being prepared. Showing the original description.
Use when filing one or more GitHub issues for planned work — "file an issue for this", "turn this plan into issues", "open a tracking issue". Covers filing everything on skyf0xx/hedgehog regardless of which repo's code changes, whether to split a plan into a tracking issue plus sub-issues, which account files the issue, labels, and acceptance criteria. For how to word an issue, see the pr-writing skill.
The English summary is being prepared. Showing the original description.
Structured GitHub issue creation from review findings or task breakdowns. Groups related findings into logical issues, applies labels, and produces issues with standard templates including summary, findings, and acceptance criteria. Designed to consume output from review-codebase or similar review skills.
The English summary is being prepared. Showing the original description.