Dev Templates & Checklists: PR, ADR, runbooks

Who it's for

You start new repositories often and rewrite the same PR template, issue forms and README every time.
You lead a small team or freelance for clients and want runbooks, ADRs and release checklists that read the same across projects.
You hand projects over to clients and need a handover checklist that covers code, accounts and infrastructure.

Not for you if your organisation already has a maintained template repository you are required to use.

Generated from the zip

What's inside

Plain Markdown and YAML, grouped by folder. Every file starts with a one-line purpose, and every blank to fill in is an <angle-bracket description>.

GitHub: a pull request template, 4 issue forms with the template chooser, Dependabot, an example CODEOWNERS file and security, support and contributing pages.
ADRs: how to use architecture decision records, a template and three invented examples.
Runbooks: a per-service runbook and team procedures for incidents, deploys, rollbacks, migrations, secret rotation and on-call handoff.
READMEs: templates for a library, web app, internal service, CLI tool, Salesforce DX project and n8n workflows.
Checklists: release, website launch, code review, security, accessibility (WCAG 2.2 AA), performance, onboarding, client handover, Salesforce deployment and API design.
Planning and postmortems: RFC, feature spec, project kickoff, estimation worksheet, postmortem template and an invented example postmortem.
Guides: how to use the templates and how to adapt them.

GitHub templates (.github): 11
ADR template and examples: 5
Runbooks: 7
README templates: 6
Checklists: 10
Planning and postmortem templates: 6
Guides: 2

In the zip · 50 files · 63 KB

CHANGELOG.md
LICENSE.md
README.md
adr/5 files
checklists/10 files
docs/2 files
github/11 files
planning/4 files
postmortem/2 files
readme/6 files
runbooks/7 files

Setup

Requirements

Nothing to install: Markdown and YAML files you copy into your repositories
GitHub for the issue forms and PR template (the Markdown templates work anywhere)
Optional: GitHub CLI (gh) to open checklists as issues; Salesforce CLI (sf) and n8n 2.x for their templates

Unzip the file and read docs/how-to-use.md.
Copy github/.github/ into the root of a repository and push it.
Open a new issue on GitHub: the template chooser shows the four forms. Open a pull request: the description is pre-filled.
Copy the README template that fits the project and fill in the <angle-bracket> blanks.
Before your next release, work through checklists/release.md.

Time to first result: about 15 minutes.

Tested with

Clean-install test passed on 2026-10-01 (darwin-arm64, node 22.23.2, npm 10.9.8): extract, base, yaml, docs, acceptance. No network access was used.

Licence

You may use this product in unlimited personal and commercial projects, including client work. You may not resell, redistribute, sublicense or share the product itself, in whole or in part, including as a template, starter kit or course material. One purchase covers one person.

The full licence is in LICENSE.md inside the zip. Site terms: /terms.

FAQ

Questions

Do the issue forms need GitHub?

Yes. The issue forms and the PR template are GitHub features. The other templates are plain Markdown and work in any wiki, docs folder or tracker.

Are the examples real incidents and decisions?

No. The example ADRs and the example postmortem are invented and labelled as such.

How do updates work?

New versions go to your Gumroad library; download them from there. Changes are listed in the CHANGELOG inside the zip.

Can I use it for client work?

Yes. Use the templates in unlimited personal and commercial projects, including client repositories. You can't resell or share the template set itself.

What about refunds?

Payment goes through Gumroad. All sales are final: the files are delivered instantly, so there are no refunds. Updates within version 1.x are free.

Where do I ask a question?

Use the contact form.

Dev Templates & Checklists