Skip to content
Modern Git AcademyMaster Git. Engineer on GitHub. Automate Everything.

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.

Who it is for

Section titled “Who it is for”

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.

The problem it solves

Section titled “The problem it solves”

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.

What you receive

Section titled “What you receive”

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. Nothing here repeats the free cheat sheets — the toolkit starts where they stop.

git/ — three decision guides

Section titled “git/ — three decision guides”
  • Merge vs rebase decision guide
  • reset / revert / restore — which one, with the deciding question for each
  • Choosing a branching strategy

github/ — seven files

Section titled “github/ — seven files”
  • 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

github-api/ — five automation files

Section titled “github-api/ — five automation files”
  • 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

actions/ — five workflow templates

Section titled “actions/ — five workflow templates”
  • 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

security/ — two files

Section titled “security/ — two files”
  • Secrets management checklist
  • Least-privilege GITHUB_TOKEN guide

ai/ — three files

Section titled “ai/ — three files”
  • Repository instructions template for Copilot and coding agents
  • Checklist for reviewing AI-generated code
  • Checklist for reviewing an AI agent’s pull request

devops/ — four files

Section titled “devops/ — four files”
  • GitOps repository structure
  • Infrastructure-as-code repository template
  • Deployment pull request checklist
  • Environment promotion checklist

What a file looks like

Section titled “What a file looks like”

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.

Pricing

Section titled “Pricing”

Most complete

Professional

$99one-time

The complete toolkit for an individual engineer.

  • Merge vs rebase, reset/revert/restore and branching-strategy decision guides
  • Annotated CODEOWNERS, pull request and issue templates
  • Repository setup and ruleset planning checklists
  • Five GitHub Actions workflow templates
  • GitHub API automation: gh api recipes, PR triage and release-notes scripts, token permissions matrix
  • Secrets management and least-privilege token guides
  • AI repository instructions and review checklists
  • GitOps and infrastructure repository templates
  • Free updates as the templates evolve

Single engineer. Use in unlimited personal and employer repositories.

Get Professional

Licence, delivery and updates

Section titled “Licence, delivery and updates”

Licence — one engineer, unlimited personal and employer repositories. Adapt freely; do not redistribute. Delivery — digital, immediately after payment. Updates — included for as long as the toolkit exists. Full terms, including refunds, are in the Terms.

Who it is not for

Section titled “Who it is not for”

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.

Free alternatives, honestly

Section titled “Free alternatives, honestly”
Free cheat sheet bundleSix printable references covering commands, recovery, review, Actions and security.
Actions Security ChecklistThe full checklist, free and complete.
Git Command AtlasSearchable command reference with cautions.
The whole curriculum300 lessons across eight pillars. Always free.

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, immediately after payment, through the checkout confirmation. If the link does not arrive, 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. Teams standardising across several engineers want the team product instead.
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?
The free Actions security checklist and the cheat sheet bundle are written to the same standard as the toolkit files, and the toolkit starts where they stop rather than repeating them.

For teams

Section titled “For teams”

Standardising Git and GitHub practice across a group is a different problem — it needs a curriculum, an assessment and standards documents, not just templates.

Engineering Team Onboarding SystemA 30-day onboarding programme with standards templates, assessments and governance checklists — for teams of up to 50.