oss-find-real-issues
Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available.
npx skills add majiayu000/claude-skill-registry --skill oss-find-real-issues --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Find Real Issues Don't wait for someone to file an issue. find real problems in the code. This skill analyzes a codebase for actual issues that maintainers would appreciate being fixed: missing tests, inconsistent patterns, silent failures, documentation gaps. You evaluate whether they're worth filing. the LLM just finds them. ## Purpose The best contributions aren't always in the issue tracker. Experienced contributors earn maintainer trust by finding and fixing problems nobody asked about. but that everyone benefits from. This skill teaches you to read code critically, spot patterns that are off, and evaluate whether a fix would be welcome. ## Prerequisites - A repo cloned locally - Basic understanding of the codebase (from `oss-prep-to-contribute` or your own exploration) - Check that the repo accepts unsolicited PRs (some don't. verify in CONTRIBUTING.md) ## Process ### 1. Check if unsolicited contributions are welcome Before analyzing anything: ```bash # Read contribution guidelines gh api repos/{owner}/{repo}/contents/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null # Check if unsolicited PRs have been merged before gh pr list -R {owner}/{repo} --state merged --limit
- Purpose
- Prerequisites
- Process
- 1. Check if unsolicited contributions are welcome
- 2. Systematic code analysis
- 3. Filter for actionable findings
- 4. Present findings to the user
- 5. Thinking gate: user evaluates each finding
- 6. Fetch issue templates
- 7. File issues or proceed to fix
- 8. Track findings
- Related Skills
- Common Rationalizations
- Red Flags
Read contribution guidelines
gh api repos/{owner}/{repo}/contents/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
Check if unsolicited PRs have been merged before
gh pr list -R {owner}/{repo} --state merged --limit 20 \
jq '[.[] | select(.authorAssociation != "MEMBER" and .authorAssociation != "OWNER")]'
Find source files without corresponding test files
find src/ lib/ -name "*.{ts,py,go,rs}" | while read f; do
done
Find exported functions that aren't tested
Find try/catch or error handling patterns and look for inconsistenciesWhat does the oss-find-real-issues skill do?
Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill oss-find-real-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.