Skills your agents can run
Plug-and-play capabilities — vetted, versioned, and runnable from any Mighty agent.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Use this skill when the user needs to work with GitHub from the command line using the gh CLI. Comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, search, API, extensions, and all GitHub operations via the terminal. Use it when the user says "gh pr", "gh issue", "create PR", "open PR", "list issues", "github cli", "gh api", "gh run", "create release", "gh search", "gh workflow", "create gist", "gh codespace", "gh repo", "create repo", "list repos", "merge PR", "review PR", "approve PR", "gh secret", "gh variable", "gh label", "gh project", "search github", "gh extension", "gh auth", "github token", "fork repo", "view checks", "rerun workflow", "download artifacts", "gh status", "list workflows".
Provenance tracking and synchronization for inherited rules, skills, and agents. Use when you need to detect drift, sync or publish prompts, manage inheritance from upstream, propagate changes, adapt rules, or check provenance.
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
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]. Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments.
Comprehensive GitHub code review with AI-powered swarm coordination
Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.
Create, edit, and review draw.io diagrams. Use for .drawio XML editing, PNG conversion, layout adjustment, and AWS icon usage.
Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.
Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.
Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements. Use when asked to 'analyze workflow logs', 'review action runs', or 'analyze GitHub Actions'.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Automate GitHub workflows with AI assistance. Includes PR reviews, issue triage, CI/CD integration, and Git operations. Use when automating GitHub workflows, setting up PR review automation, creating GitHub Actions, or triaging issues.
Git-Notes-Based knowledge graph memory system. Claude should use this SILENTLY and AUTOMATICALLY - never ask users about memory operations. Branch-aware persistent memory using git notes. Handles context, decisions, tasks, and learnings across sessions.
Reliably obtain a non-empty unified git diff for the current work using safe fallbacks (git diff, origin/master...HEAD, origin/main...HEAD) and return structured JSON containing the diff and the command used.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.