We use cookies to understand how the site is used and to display ads. Analytics and advertising only run after you accept. You can change your choice anytime. Privacy policy

Skip to content
devvkit

devvkit / dev

First PR Checklist

Track your first open source contribution step by step: saved in your browser.

First PR Checklist

0%

0 of 22 steps complete. Progress saved in your browser: survives restarts.

Before You Start

0/6 complete

Making the Change

0/6 complete

Opening the PR

0/6 complete

After the PR

0/4 complete

Quick Reference

Good PR title patterns:

  • fix: handle empty state in user profile
  • feat(cli): add --json output flag
  • docs: clarify install steps for Windows
  • refactor: extract auth middleware

Description template:

## What does this PR do? Fixes #<issue-number> ## How was it tested? - [ ] Unit tests written/updated - [ ] Local run verified - [ ] Lint & type-check pass ## Checklist - [ ] Commit messages follow Conventional Commits - [ ] No unrelated changes - [ ] Docs updated if behavior changed

share this tool

Make your first open source pull request with a guided 20-step checklist. Four stages: preparing, coding, opening the PR, and following up: each with concrete actions, a progress bar, and markdown export. Progress saves automatically in your browser.

>[x]Features
  • -20 actionable steps across 4 stages
  • -Progress bar with per-stage breakdown
  • -Auto-saved progress in browser local storage
  • -Export progress as markdown
  • -Conventional Commits and PR description templates
>>Use Cases
  • >First-time contributors working through their first PR
  • >Newcomer onboarding in open source study groups
  • >Mentoring: a shared checklist for contribution training
  • >Documenting personal contribution progress

Frequently Asked Questions

>Is my progress saved??
Yes, your checklist progress is stored in your browser's local storage under devvkit_first_pr_checklist. It survives page reloads and browser restarts on the same device.
>Where should I find my first issue??
Look for issues labeled good first issue, help wanted, or beginner-friendly. Filter GitHub search by these labels, check the curated issues on the devvkit Open Source hub, or look for repos with active maintainers and short response times.
>How do I write a good PR title??
Follow Conventional Commits: prefix with type (fix:, feat:, docs:, refactor:, perf:, test:) plus a concise summary. Example: fix: handle empty state in user profile. This keeps history readable and works with semantic-release automation.
>What should I do if my PR is not reviewed??
Wait 48 hours, then politely bump the thread mentioning a maintainer. Meanwhile respond to any CI failures, keep the branch rebased, and offer to make requested changes quickly. Reviewers usually prioritize contributors who are responsive.