Should I Contribute

Research any open-source repository end to end and answer the core question — SHOULD YOU contribute to it? — with a GO / NO-GO / GO-IF verdict backed by evidence: snapshot, momentum, contribution landscape (PR acceptance rates, outside-contributor merge rates, first-timer outcomes), issue health, governance, community sentiment, and a final go/no-go recommendation. Use when the user asks 'should I contribute to X', wants a before-I-contribute due-diligence check on a project, asks whether a project accepts outside PRs, wants contribution-health numbers like PR merge rates or stale-PR counts, o

8 starsGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add definitelynotchirag/should-i-contribute --skill should-i-contribute

Manual install

git clone --depth 1 https://github.com/definitelynotchirag/should-i-contribute.git /tmp/should-i-contribute
mkdir -p ~/.claude/skills
cp -r /tmp/should-i-contribute/. ~/.claude/skills/should-i-contribute

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Should I Contribute? — repository contribution research

Research ANY open-source repository and produce a detailed analysis report: what it is, how healthy it is, how it actually treats outside contributors, what a PR/issue from a stranger would experience — and, at the end, a clear GO / NO-GO / GO-IF verdict on whether YOU should contribute. The core insight: PR *acceptance* is a much better signal of open-source health than PR *volume* — a project can look busy while quietly ignoring everyone outside the core team.

## Output contract

Deliver ONE markdown report with these sections (see Report template at the end):

1. Executive summary — 3-6 bullet verdict (GO / GO-IF / NO-GO) with the headline numbers
2. Snapshot — identity, stats, license, stack
3. Momentum — is the project alive and shipping?
4. Contribution landscape — the core: open-PR census, age buckets, outside-author share, merge rates, first-timer outcomes
5. Issue health — open issues, stale bugs, "documented bug with unmerged fix" search
6. Governance & maintainability — docs, templates, who actually merges, bus factor
7. Community sentiment — HN/Reddit/Discord signals, maintainer quotes
8. Risks & opportunities for the requester
9. Methodology & caveats — every number gets its source and sample

Every claim MUST be grounded in a number you computed or a quote you read. No vibes.

## Setup

### Target and API access (GitHub, the common case)

Read the full skill on GitHub

Details

Skill name: should-i-contribute
Repository: definitelynotchirag/should-i-contribute
License: MIT
Repo updated: 10 August 2026

FAQ

What does the Should I Contribute skill do?

How do I install the Should I Contribute skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add definitelynotchirag/should-i-contribute --skill should-i-contribute. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Should I Contribute popular?

It lives in definitelynotchirag/should-i-contribute, which has 8 GitHub stars and 0 forks.

Related skills

Limit Up Dao

laozdao/limit-up-dao

老子道涨停股批量归因分析Skill。基于开源大模型，输入日期自动获取当日所有涨停股票数据，逐一输出多维度归因分析报告。GitHub https://github.com/laozdao/limit-up-dao。触发场景：用户要求分析某日涨停股、批量涨停归因、今日涨停复盘、涨停板原因分析、连板股分析等。

Git & Code Review

Github Pages Deploy

AIPMAndy/github-pages-deploy-skill

Use when user wants to deploy a static website to GitHub Pages, mentions "一键部署", "GitHub Pages", or needs to publish HTML/web content to a public URL. Triggers on requests like "部署网站", "发布到GitHub", "做个网页并上线".

Git & Code Review

Worktree Closeout

leonsong09/worktree-closeout

Use when the user asks for worktree closeout, branch closeout, parallel closeout, worktree janitor, 工作树收口, 分支收口, or 并行收口, especially when work spans multiple Codex sessions and you need a date-based scan of open worktrees, closeout status, suggested merge/prune order, and prompt-ready handoff instructions.

Git & Code Review

Feature

pardeep-kumar94/claude-idea-to-pr

Runs a feature end to end — grill, prototype, spec, tickets, build with TDD, code review, PR — resuming wherever the feature stands and stopping at each decision that belongs to the user, while keeping the Feature Line board current. Use when the user says /feature, wants to start or continue building a feature, asks what's next on a feature, or wants its board status updated.

Git & Code Review

Blitz

ADM-NKH/claude-blitz

A continuously-firing background work runner for Claude Code. Queue real tasks ("/blitz add"), track long-term goals ("/blitz goal add"), and enable per-project audit rotations ("/blitz audit enable"). Blitz fires on a configurable cadence with a per-project idle gate, decomposes goals into increments on a long-lived branch, and persists every fire's output to ~/blitz/runs/<timestamp>/. Includes commands to manage the backlog, goals, audits, schedules, and kill switches (off/on/skip).

Git & Code Review

Mobileconfig Builder

GodModeAI2025/mobileconfig-builder

Erstellt produktionsreife .mobileconfig-Dateien (Apple Configuration Profiles) für macOS, iOS, iPadOS, tvOS, watchOS und visionOS. Holt die YAML-Schemas aus github.com/apple/device-management (Branch `release`) in einen lokalen Cache und validiert jeden Payload gegen diesen Cache-Stand, der liegen bleibt, bis `fetch_schema.py --refresh` ihn neu holt. Führt bei Bedarf einen Interview-Flow (Plattform → PayloadType → Pflichtfelder) und erzeugt eine korrekt strukturierte, optional PKCS#7-signierte .mobileconfig zum Direkt-Aufspielen via MDM, Profile Manager, AirDrop oder USB. Verwende diesen Skill

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.