Skills your agents can run

Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.

Audits and improves CLAUDE.md files by scanning repositories and evaluating quality against templates. Outputs a quality report with scores and applies targeted updates. Use for CLAUDE.md maintenance and optimization or when reviewing what project instructions should contain.

Performs thorough code reviews following best practices. Use when reviewing pull requests, checking code quality, or ensuring coding standards compliance.

Automated CI/CD pipeline setup with GitHub Actions, deployment strategies, and automation workflows. Use for build automation, testing, and deployment.

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

Use this skill whenever preparing agentsmesh for an npm release — whether first publish, patch, minor, or major. Triggers on: 'prepare release', 'ready to publish', 'ship version', 'release prep', 'get this to npm', 'bump version', 'cut a release', 'what's needed to publish'. Runs a strict ordered checklist: test suite health → timing hardening → CI/CD presence → community health files → changesets → CHANGELOG quality → package contents → README badges → final gate → generate to targets. Do not skip this or work from memory — execute every phase in order and fix gaps before moving on.

Extract and organize Claude Code session history into project .chats directory. Use when users want to document their Claude sessions, export conversation inputs, or maintain a log of instructions given to Claude.

Checks for updates to remote GH site for palladius/gemini-cli-custom-commands. Use Ruby code to check for newer/older version.

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

Deep-dive analysis of GitHub projects. Use when the user mentions a GitHub repo or project name and wants to understand it — triggered by phrases like "Take a look at this project", "Check out XXX", "What is this project like", "Analyze the repo", or any request to explore/evaluate a GitHub project. Covers architecture, community health, competitive landscape, and cross-platform knowledge sources.

Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chain three agents (Forker, Sanitizer, Packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'.

An evidence-first audit workflow for ECC Tools burn and billing. Used to investigate runaway PR creation in the ECC-Tools repository, quota bypass, paid-model leakage, duplicate jobs, or GitHub App cost spikes.

Update the release notes file at `apps/docs/content/releases/next.mdx` based on PRs merged to main since the previous release, or archive `next.mdx` to a versioned file when a new version is published.

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.

Guide for recovering lost Git commits, resolving detached HEAD states, and fixing common Git repository issues. This skill should be used when users need help recovering from Git mistakes such as lost commits, detached HEAD situations, accidental resets, or when commits appear to be missing from branches.

Create high-quality git commits: review and stage intended changes, split diffs into logical commits, and write clear commit messages (including Conventional Commits). Use this when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

MUST be used when creating pull requests. Handles context gathering, title generation (conventional commit format), body formatting, and PR creation via GitHub CLI. Creates PRs as drafts by default. Triggers on: "create PR", "open PR", "ready for review", "push for PR", "send for review".

Git workflows, branching strategies, commit message conventions, and the pull request process.

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

Search GitHub code, repositories, issues, and PRs via MCP