Loading...
Loading...
Found 1,851 Skills
Fetch unresolved PR comments (both code-level and PR-level), validate issues, and fix them. Also checks CI status and fixes failing tests, lint errors, and build issues. Use when reviewing and addressing GitHub PR feedback. Filters out resolved comments, keeps only the last claude[bot] comment per thread, validates issues, posts review report as a PR comment, then fixes validated issues.
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.
Skills for accessing and searching docs in DeepWiki/GitHub’s public code repositories can help users understand open-source project source codes, and users can also ask questions directly about the code docs.
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.
Triages new GitHub issues — classifies, reproduces bugs, attempts conservative fixes, and comments. Use when a new issue is opened and needs automated triage.
Stream-backup active recordings to GitHub. TRIGGERS - backup recording, sync cast, streaming backup.
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
GitHub backup for OpenClaw workspace. Use when user says "同步", "备份", "backup", "sync", "push to github", or asks about backup status/history/failures. Manages git-based full backup of ~/.openclaw to GitHub.
Create structured GitHub issues from conversation context using gh CLI
This skill should be used when the user asks to "create an issue", "file a bug", "create a feature request", "open a GitHub issue", "report a bug", "request a feature", "create a task", "break this into issues", or describes a feature/bug they want tracked in GitHub. Guides interactive issue creation with structured templates, workspace change attachment, and optional autonomous label for the automated pipeline.
Systematically explore and evaluate a library, tool, or GitHub repo in an isolated scratch environment. Use this skill whenever the user asks to "try", "evaluate", "explore", or "kick the tires" on a library/repo/tool, especially when they provide a GitHub URL, npm/pip package name, or repo shorthand like "owner/repo". Use it when they want real primitives, failure modes, and composability beyond quickstarts before deciding on integration. Produces runnable scratch/ scripts demonstrating key primitives, a composition script, and a Tutorial.md with honest findings. This is NOT for full integration into an existing codebase.