Loading...
Loading...
Found 2,521 Skills
Pick a random contributor from a GitHub repository using the GitHub API or repository pages (no auth required for public repos).
Commit all changes, push to remote, and create or update a GitHub PR for a story branch. With the draft-PR-first workflow, this is primarily used for incremental pushes to existing draft PRs. Also handles legacy cases where no PR exists yet.
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, or as a follow-up to the user-story-implementer skill.
Collaboration workflow for GitHub Issue handling. Used when users receive an issue that needs analysis and response. Through the four-step process of "Diagnosis → Qualification → Decision → Response", produce accurate root cause analysis and appropriate user responses from an issue, avoiding misjudgment of problem types or unprofessional responses.
Deterministic 3-phase GitHub PR review comment extraction: Authenticate, Mine, Validate. Use when mining tribal knowledge from PR reviews, extracting coding standards from review history, or building datasets for the Code Archaeologist agent. Use for "mine PRs", "extract review comments", "tribal knowledge", or "PR review history". Do NOT use for analyzing patterns, generating rules, or interpreting comments — that is the Code Archaeologist agent's responsibility.
GitHub 审视 - Read-only GitHub triage for issues and PRs. 触发条件/Triggers: 需要分析 GitHub Issues 或 PRs、生成审查报告、或分类问题。 核心原则/Core Principles: - 只读不写/Read-only: 永不修改 GitHub 状态 - 证据支持/Evidence: 每个结论都需要 GitHub permalink 证明 - 并行分析/Parallel: 每个 Issue/PR 独立后台任务 - 报告输出/Reports: 写入临时目录，不操作 GitHub 命令/Commands: - /审视 analyze <repo> - 分析仓库所有开放 Issue 和 PR - /审视 issues <repo> - 只分析 Issues - /审视 prs <repo> - 只分析 PRs - /审视 <URL> - 分析特定 Issue 或 PR - /analyze <repo> - English command 能力/Capabilities: GitHub 数据读取、问题分类、证据收集、报告生成、后台并行处理。
Used when the user requests to search technical documents, look up code examples, check web resources or view GitHub repository information.
This skill should be used when a user wants to create, draft, or plan a GitHub Epic issue — for example "write an epic", "I want to define a new initiative", "scope out this strategic project", "turn this idea into an epic", "plan work that spans multiple features", or "start from a bounded context". Also use when the user asks to define domain outcomes, capture a large initiative before breaking it into features, or describe work in terms of business goals rather than technical tasks.
Turn messy Unity or Unreal build/release automation into one bounded game-pipeline packet after naming the signal tier first: fast branch-gate CI, nightly/package- candidate builds, or release/certification candidates. Use when a game team needs to design or repair GitHub Actions, Unity Build Automation, Jenkins, TeamCity, or similar CI for engine builds — especially when they mention flaky packaging, cache superstition, giant build-job blobs, slow cook / package cycles, artifact confusion, SDK/signing drift, or manual candidate promotion that should become reproducible. Route one red log first-pass diagnosis to `game-build-log-triage`.
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.
Ask questions and read documentation about any GitHub repository using DeepWiki MCP. Use when you need to understand a codebase, find specific APIs, or get context about a repository.
Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.