← ClaudeAtlas

maintainer-good-first-issuelisted

Finds small, well-scoped tasks a newcomer can finish in an afternoon, from the codebase itself (TODOs, missing tests, unclear errors, doc gaps) and from open issues, then writes starter issues with context, file pointers, acceptance criteria and a "how to get started" section. Drafts them to a file; creates them on GitHub only after the user confirms. Use when the user says "find good first issues", "I want more contributors", "write starter issues", "what can a newcomer work on", "label beginner-friendly issues", or "help wanted tasks for hacktoberfest".
vivekbhange-hub/maintainer-skill · ★ 0 · AI & Automation · score 75
Install: claude install-skill vivekbhange-hub/maintainer-skill
# Good first issues A good first issue is not "an easy issue". It is a task with one obvious place to start, a clear finish line, and a reviewer who already knows what the answer looks like. This skill finds those tasks and writes them up so a stranger can pick one and open a PR without asking a question. ## Steps 1. **Learn how to build and test.** Read README, CONTRIBUTING.md, and the build manifest (`package.json` scripts, `pyproject.toml`, `Makefile`, `Cargo.toml`, `go.mod`, CI workflow). Record the exact install and test commands. If you cannot find a test command, say so; every starter issue will need one. 2. **Mine candidates from the code.** Use Grep and Glob, skipping vendored and generated folders: - `TODO|FIXME|XXX|HACK` comments with a concrete ask (skip vague ones like "TODO: refactor"). - Public functions with no test (compare `src/` names against `tests/` mentions). - Error messages that do not say what to do next (`raise ValueError("invalid")`). - CLI flags or config keys present in code but missing from docs, and the reverse. - Type hints, docstrings, or examples missing on a small public module. - Deprecation warnings the project emits to itself in test output. 3. **Mine candidates from issues.** ``` gh issue list --state open --limit 200 --json number,title,body,labels,comments,assignees ``` Keep issues that are confirmed, unassigned, have no open PR linked, and need a change in at most 2-3 files. Check for lin