Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Analyzes a GitHub repo's history and culture before you file an issue, open a PR, or comment on a thread. Surfaces contributor concentration, merge velocity, rejection patterns, and existing related discussions. Produces a concrete recommendation on how to proceed.
Going in blind risks submitting duplicate issues or PRs that get closed for reasons already documented in the repo's history.
When to use it
- Checking if a feature PR will be accepted before writing code
- Finding duplicate issues before filing a new bug report
- Understanding why similar PRs were previously rejected
- Gauging maintainer responsiveness to a feature request
- Deciding whether to comment on an existing thread or open a new one
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Should I open a PR to add plugin support to owner/repo?
- 1Fetch repo metadata: stars, forks, license, last push date, archived status
- 2Pull top 10 contributors to assess governance concentration
- 3Search open and closed issues and PRs for 'plugin' to find prior discussions
- 4Review last 50 closed-without-merge PRs for rejection patterns and maintainer reasoning
- 5Synthesize findings into a labeled recommendation with concrete next steps
FILE-ISSUE-FIRST — maintainer is responsive but feature not yet discussed. Recommended: open an issue referencing #42 where a related request was acknowledged, gauge interest before coding.
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.