Loading...
Loading...
Found 1,586 Skills
Automated code review assistant that analyzes GitHub pull requests and code changes. Use when: (1) user shares a GitHub PR URL and wants a code review, (2) you need to review code for bugs, security issues, or best practices, (3) performing automated code quality checks before merging, (4) analyzing code diffs for potential improvements.
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.
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.
Upload images to img402.dev for embedding in GitHub PRs, issues, and comments. Images under 1MB are uploaded free (no payment, no auth) and persist for 7 days. Use when the agent needs to share an image in a GitHub context — screenshots, mockups, diagrams, or any visual. Triggers: "screenshot this", "attach an image", "add a screenshot to the PR", "upload this mockup", or any task producing an image for GitHub.
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
Use prefered practices when using git. Use when Codex needs to perform actions with git or Github.
Iteratively gets a GitHub pull request's checks green. Detects the PR for the current branch or uses a provided PR number, waits for every check on the latest head SHA to appear and finish, investigates failing checks, fixes actionable code or test issues, pushes, and repeats. Escalates with a precise blocker when failures are external, flaky, or not safely fixable. Use when a PR still has unsuccessful checks after review fixes, including after greploop.
Use gitcrawl for OpenClaw issue and PR archive search, duplicate discovery, related-thread clustering, and local GitHub mirror freshness checks.
Search and download specific files/folders from GitHub repositories directly from terminal using ghgrab, without full clone. Covers install, interactive browsing, release asset download, and automation-safe usage patterns.
Researches any project idea against live data from GitHub and Dev.to to surface what already exists, how mature the space is, and where the real opportunity lives. Use when a developer describes something they want to build and wants to know if it's been done before. Triggers on phrases like "validate my idea", "has this been built", "is this already a thing", "what exists for X", "should I build this", "is this idea original", "check if my project exists", "what are the alternatives to what I want to build", "is the market saturated for X", or any request to research the competitive landscape before starting a project.
Generate and publish blog posts from any project to kelegele/agent-blog. ZERO DEPENDENCIES — does NOT require Node.js, pnpm, git, or any local build tools. Works with only a browser and a GitHub token. Triggers on: "写篇博客", "blog this", "发博文", "publish blog", "把项目写成文章", "写篇文章", "blog it", "post article", "新文章", "new blog post", "blog this project", "发一篇博文", "写一篇博文", "blog post about this", "edit blog post", "修改文章", "更新博文", "edit article". Collects project context, collaborates on outline, writes Markdown with correct frontmatter, validates article format, generates a standalone HTML preview by reading live blog source, manages draft/review/publish flow. Pushes to kelegele/agent-blog main branch. Vercel auto-deploys on push. Use this skill whenever the user expresses intent to write about their current work as a blog post.
Use when an agent is asked to perform GitHub work in a repository that should follow using-github conventions