正在浏览:

sperezintexas

Diagnose GitHub Actions CI failures and suggest fixes. Use when the user reports CI failed, GitHub job failed, Actions failed, build failed on remote, upload artifact failed, or pastes a failure from the Actions tab.

agentjido

Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflow_dispatch) and manual release flows. Uses git_ops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.

fgarofalo56

Comprehensive GitHub operations via gh CLI. Manage repositories, issues, pull requests, Actions workflows, code security, discussions, projects, gists, notifications, and more. Use for any GitHub-related task including creating PRs, reviewing code, managing issues, monitoring CI/CD, and analyzing security alerts.

deadlock-mod-manager

Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs. Use when needing to understand how a library works internally, debug dependency issues, or explore package implementations.

jacky-wong9273

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

blockscout

Expert review of an implementation plan against a GitHub issue/enhancement description (provided as a local file or a GitHub issue URL) and the current repository codebase. Use when asked to critique a plan for correctness, completeness, codebase alignment, risks, and test/rollout readiness (do not implement).

msalganik

This skill should be used when the user wants to commit their work to git and push to GitHub. It guides through reviewing changes, crafting meaningful commit messages following project conventions (including Conventional Commits when detected), creating commits with security checks, and pushing to remote repositories.

ainergiz

Create GitHub issues with duplicate detection and codebase analysis. Use when you discover a bug, improvement, or issue that wasnt in the original scope/spec during development. Triggers on phrases like create an issue, file a bug, this should be tracked, we should fix this later, out of scope issue, noticed a problem, found a bug.

danielnewman09

Convert a ticket markdown file from tickets/ into a GitHub Issue, preserving all content and metadata. Accepts bare number (0039a), full name (0039a_energy_tracking_diagnostic_infrastructure), or with .md extension. Creates labels, resolves cross-references, updates parent issues, and closes completed tickets. For work tickets, creates workflow phase sub-issues (Design, Math, Prototype, Implementation). For investigation/debug tickets, creates debug phase sub-issues (Investigate, Diagnose, Fix, Verify).

majiayu000

This skill should be used when the user asks to create a pull request, create PR, open PR, create an issue, file an issue, create a GitHub issue, create a Claude Code issue, report a bug in Claude Code, create a Codex issue, report a bug in Codex CLI, create a discussion, start a GitHub discussion, or mentions OSS contribution workflows.

Colin4k1024

Maintain the Oris Rust agent runtime with an issue-driven GitHub workflow. Use when Codex is working in the Oris repository and needs to pick up a GitHub issue, turn the issue into scoped code changes, run Rust validation such as cargo fmt and cargo test, publish the oris-runtime crate to crates.io, close the completed issue, and continue to the next iteration.