Skip to content

Professional Toolkit

The curriculum on this site teaches the reasoning. The toolkit is the artefacts — the files you would otherwise write from scratch each time you set up a repository.

Before you buy

Who it is for
An engineer who sets up or tidies whole repositories — branching, reviews, rulesets, tokens, automation — and would rather adapt a reviewed file than assemble one each time.
What it helps you do
Getting a repository into a defensible state: who reviews what, which rules apply, which token permissions are needed, and what the pull request should ask for.
What you receive
Twenty-nine files in seven folders (git, github, github-api, actions, security, ai, devops) plus a README that links each file to the lesson explaining it. Markdown, YAML and shell — nothing proprietary.
What you configure yourself
All of it is a starting point: CODEOWNERS paths, ruleset choices, workflow versions and pinned action SHAs are yours to set. Each file opens with what it assumes and what to change first.
Price
$19.99 one-time. No subscription, no account, nothing recurring.
Delivery
A ZIP from a download page that opens the moment Stripe confirms payment, and keeps working for updates. No account, nothing to install. Order help covers a download page that does not open.
Licence, updates, refunds
Single engineer. Use in unlimited personal and employer repositories. Updates included. Full refund within 14 days of purchase, on request — reply to your Stripe receipt or use the contact page with your support reference. No questions asked; the files are yours to delete. Full terms.

Download a file from the toolkit, free — the same standard as the rest, before you spend anything.

Engineers who set up repositories repeatedly and would rather adapt a considered starting point than assemble one each time — and who want the reasoning behind each file one link away.

Every new repository needs the same dozen decisions made again: what CODEOWNERS should say, what the CI workflow’s permissions block should contain, which ruleset options to enable, how the release workflow should be gated. The decisions are documented across this site. Assembling them into files takes an afternoon each time, and the afternoon is where the mistakes creep in.

Twenty-nine files in seven folders, plus a README. Each carries a short note on what it assumes and what to change first, and the README links every file to the lesson that explains it. The toolkit starts where the free cheat sheets stop: one file is in both, deliberately — gh-api-pagination-recipes.md is published free, byte for byte, so you can judge the standard of the other twenty-eight before paying. The remaining free downloads (a CODEOWNERS starter, a branching decision matrix, a repository health checklist, the aliases file and the Actions security checklist) are shorter, separate files, not extracts from the paid ones.

  • Merge vs rebase decision guide
  • reset / revert / restore — which one, with the deciding question for each
  • Choosing a branching strategy
  • Annotated CODEOWNERS template
  • Pull request template
  • Issue templates: bug report, feature request, and a config.yml that disables blank issues
  • Repository setup checklist
  • Ruleset planning checklist
  • gh api pagination and filtering recipes — ten working patterns for --paginate, --slurp and --jq, with the mistakes each avoids
  • Pull request triage script: needs-review, re-review-after-changes and stale lists, with an --apply mode that only labels
  • Release notes script: merged pull requests since the last tag, grouped by label, ready for gh release create
  • Fine-grained token permissions matrix — 24 tasks, the exact permission each needs and nothing more
  • GitHub App vs personal access token decision guide, with a tested installation-token recipe
  • CI starter, with least-privilege permissions and a checkout that keeps merge-base tooling working
  • Reusable workflow, with a versioning scheme
  • Release workflow, gated by environment, with provenance
  • Security scanning: dependency review, CodeQL and secret scanning
  • Docker build and push: test stage as a gate, Git-derived tags, provenance attestation
  • Secrets management checklist
  • Least-privilege GITHUB_TOKEN guide
  • Repository instructions template for Copilot and coding agents
  • Checklist for reviewing AI-generated code
  • Checklist for reviewing an AI agent’s pull request
  • GitOps repository structure
  • Infrastructure-as-code repository template
  • Deployment pull request checklist
  • Environment promotion checklist

Every template opens with what it assumes and what to change. From the CI starter:

# CI starter workflow — Modern Git Academy Professional Toolkit
#
# A correct baseline: least-privilege token, pinned actions, sensible caching,
# and a checkout that is cheap without breaking merge-base tooling.
#
# Before using:
# 1. Replace the setup step with your language's.
# 2. Replace the pinned SHAs with current ones (see note at the bottom).
name: CI
on:
push:
branches: [main]
pull_request:
# Start read-only. Individual jobs widen this if they genuinely need to.
permissions:
contents: read

The comment is the point. A template you cannot see the reasoning for is one you will misapply.

Licence — one engineer, unlimited personal and employer repositories. Adapt freely; do not redistribute or resell the bundle; each engineer who wants it as their own starting point needs a purchase. Delivery — a ZIP from a download page that opens the moment Stripe confirms payment and stays valid; order help covers the case where it does not open. Updates — included, published to the same download page. Refunds — a full refund within 14 days of purchase, on request. Full terms are in the Terms; the price is at the top of this page.

If you are learning Git, this is the wrong purchase. Work through the curriculum and the labs — both free, and both more useful to you right now than a set of templates.

If you enjoy writing your own tooling, you will probably prefer to. The lessons explain every decision these templates encode.

If you need one specific checklist, several are published free — the Actions security checklist is the fullest.

Purchases, downloads and refunds: admin@moderngitacademy.com. Include the Stripe receipt for anything about an existing order.

Already bought? Order help covers a download page that did not open, re-downloading, updates and refunds.

Frequently asked questions

What exactly do I receive?
A download containing twenty-nine files in seven folders — git, github, github-api, actions, security, ai and devops — plus a README that maps each file to the lesson explaining it. Markdown, YAML and plain text; nothing proprietary, nothing that needs an account to open.
How is it delivered?
Digitally: the moment Stripe confirms payment you are sent to your download page, which stays valid for updates. If it does not open, contact us with your receipt.
What is the licence?
One engineer, unlimited repositories — personal and employer. You may adapt every file freely. You may not redistribute or resell the bundle. Each engineer who uses it as their own starting point needs a purchase.
Do I get updates?
Yes, included. Action versions move and GitHub features change; when a template is revised, the revision is yours.
What is the refund policy?
Refund terms are stated in the Terms and at checkout. If you are unsure whether the toolkit fits, the free alternatives below are complete enough to decide.
Is anything from the free site moving behind this?
No. Every lesson, lab, tool and checklist that is free stays free. The toolkit is the artefacts the lessons describe — files you could write yourself from the lessons, assembled and annotated so you do not have to.
Can I see a sample first?
Yes — one of the twenty-nine files is published free and in full: gh-api-pagination-recipes.md, the same file that ships in the bundle. The free Actions security checklist and the cheat sheet bundle are written to the same standard.

The toolkit’s five Actions templates are starting points. For the full implementation set — twenty workflows covering CI for five languages, containers, Terraform, Ansible, security scanning, releases, Pages, Kubernetes and OIDC for three clouds, plus reusable workflows — the Vault is the focused product. Neither repeats the other.

Focused on GitHub ActionsGitHub Actions Production Workflow VaultTwenty production workflows, three reusable workflows, a composite action, fixtures and the documentation to run them — SHA-pinned and least-privilege throughout.