Branches, rebase, merge, conflicts, PRs, code review, GitHub Flow, Actions, releases.
Before starting, we run a 1-minute tech check — microphone, ambient noise, connection. If your setup isn't good enough, the test is fully refunded.
Prove in 15 minutes that you actually know Git and GitHub — branching strategies, rebase, PRs, Actions — not just that you've pushed commits to main.
The Plume Git & GitHub badge is a 15-minute AI-led oral exam that probes your real command of version control workflows: branching strategies (trunk-based, GitHub Flow, Git Flow), complex conflict resolution, interactive rebase, cherry-pick, reflog, and CI/CD automation through GitHub Actions. The AI examiner doesn't stop at "what's the difference between merge and rebase" — it pushes you on concrete situations you've navigated, tradeoffs you've made under pressure, and architectural decisions you've defended in a real team.
What makes this badge credible is the format. Anyone can check "Git" on their LinkedIn profile after pushing a few commits on a solo side project. Here, you need to articulate why you chose a squash merge over a rebase, how you untangled a diverging history without blowing up a colleague's branch, or which branch protection rules you put on main for a team of ten engineers. The conversation is transcribed and scored by Claude Opus, which produces a 0-100 score, a proficiency level (Novice, Proficient, Advanced, Expert), and a detailed written report you can share with a recruiter, a hiring manager, or your own team.
This badge is built for developers, DevOps engineers, tech leads, and SREs who use Git and GitHub daily and want external proof of their level — whether they're job hunting, angling for a promotion, or simply trying to stand out in a field where "strong Git skills" means nothing without evidence.
Here are the concrete dimensions the AI examines during the 15-minute oral.
Ability to design and justify a branching strategy for a given context: trunk-based development for continuous deployment teams, GitHub Flow for fast-moving web projects, Git Flow for cadenced release cycles. Includes long-lived branch management, feature flags, and merge queues.
Hands-on command of interactive rebase (squash, fixup, reword, drop), cherry-pick across branches, reflog to recover lost commits, and git bisect to pinpoint regressions. Solid understanding of the risks of rebasing shared branches and disciplined use of force-push.
Practice of well-scoped PRs, atomic commits, clear PR descriptions, and constructive review feedback. Familiarity with GitHub-specific features: suggested changes, draft PRs, required reviews, CODEOWNERS files, and PR templates that actually get used.
Configuration of branch protection rules (required status checks, required reviews, dismiss stale reviews, restrict force-push), GitHub rulesets, merge queues, and team-level permission management. Ability to enforce quality gates without slowing down the team.
Design of Actions workflows with jobs, steps, matrix strategy, caching, artifacts, and secrets. Integration with deployment environments (staging, production), org/repo/environment-level secret management, and advanced triggers (workflow_call, workflow_dispatch, path-filtered pushes).
Handling merge conflicts on text and binary files, using git rerere, understanding merge strategies (ours, theirs, octopus), and resolving history divergence after a rebase or reset gone wrong. Familiarity with both visual tools (VSCode, IntelliJ) and the command line.
Creating and managing GitHub releases, semantic tagging (semver), automating changelogs with GitHub Actions or Release Please, and handling pre-releases. Working knowledge of GitHub Packages and artifact publishing tied to tags.
Practical use of GitHub Codespaces, Copilot, Dependabot, GitHub CLI (gh), REST and GraphQL APIs, webhooks, and GitHub Apps. Critical perspective on GitHub vs GitLab vs Bitbucket tradeoffs depending on team size, security requirements, and workflow preferences.
Final scoring is performed by Claude (Anthropic), which reads back the full transcript and applies this weighted criteria grid.
Precision in explaining advanced Git commands (interactive rebase, reflog, cherry-pick, bisect, rerere), understanding of Git's internal data model (DAG, blob/tree/commit/tag objects), and ability to reason about history and its implications for team workflows. This is the core of the badge.
Quality of PR practices (scoping, description, review), familiarity with GitHub collaboration features (CODEOWNERS, branch protection, merge queue, draft PRs), and demonstrated ability to improve the velocity and quality of a shared engineering workflow.
Ability to design efficient GitHub Actions workflows, manage secrets and deployment environments, and automate releases. Understanding of triggers, build matrices, caching strategies, and pipeline security best practices.
Ability to choose the right branching strategy for the context, identify the limits of common approaches (monorepos, squash merges, rebasing in shared branches), and argue versioning architecture decisions against real team constraints and release cadence requirements.
Quality of verbal explanation on complex technical topics: ability to make Git's model accessible, draw on concrete personal examples, and structure a workflow explanation in a way that's clear to a peer, a recruiter, or a junior developer asking for help.
A Plume session takes about 20 minutes, from tech check to badge delivery.
The AI confirms your mic is working, your connection is solid, and you're in a quiet space. No screen sharing needed — the exam is entirely audio. Feel free to have a terminal or GitHub open on the side to jog your memory on specific commands or examples.
The examiner asks you to introduce yourself briefly: your current role, your team setup, the size of the main repo you work on, and how you use Git day-to-day. This helps calibrate the depth and focus of the questions that follow.
The core of the exam: the AI explores 4 to 6 themes from the following — complex conflict resolution, branching strategy, rebase and history manipulation, PR and code review practices, GitHub Actions, and critical perspective on the ecosystem. It adapts to your answers and probes harder on anything that sounds fuzzy.
The examiner asks one or two questions about limits you've personally hit: when rebase is the wrong tool, when a monorepo stops scaling, or what GitHub genuinely doesn't do well in your experience. This critical angle is weighted positively in scoring.
The transcript is passed to Claude Opus, which produces a 0-100 score, a proficiency level (Novice/Proficient/Advanced/Expert), and a detailed report. Your Git & GitHub badge with a shareable URL lands in your inbox as soon as the analysis is done, usually within an hour.
Your score out of 100 translates into a level a recruiter can grasp at a glance.
You use Git mainly solo or on small projects: git add, commit, push, pull, and the occasional merge or stash. You struggle to explain the difference between rebase and merge, you avoid conflicts, and you haven't really worked in a structured collaborative GitHub workflow with PRs and code reviews.
You work with Git and GitHub in a team: you create branches, open PRs, do code reviews, and you can resolve straightforward conflicts. You have a working understanding of GitHub Flow and use git rebase occasionally. You may have set up basic GitHub Actions workflows, but advanced CI/CD architecture is still out of reach.
You design your team's branching strategy, you're comfortable with interactive rebase, cherry-pick, and reflog, and you configure branch protection rules and CODEOWNERS without thinking twice. You build GitHub Actions workflows with matrix builds, caching, secrets, and deployment environments. You can explain the tradeoffs between trunk-based development and Git Flow to a skeptical colleague.
You have a clear mental model of Git's internal data structure (DAG, objects), you've managed monorepo migrations or complex history rewrites, and you run GitHub governance at org scale (rulesets, org-level secrets, GitHub Apps, GraphQL API). You make versioning architecture calls that balance release velocity, security requirements, and CI performance — and you can defend them under scrutiny.
No degree or years of experience required to take the badge. Here are the profiles it makes the most sense for.
You use Git and GitHub every day but you've never had external proof of your level. This badge lets you show concretely that you can handle PRs, rebase, and collaborative workflows — not just claim it on your resume.
Mastery of GitHub Actions, branch protections, and CI/CD pipelines is central to your role. This badge proves to hiring teams that you can automate releases and govern a repo at scale, not just push code and hope for the best.
You define your team's branching strategy, PR standards, and GitHub governance. This badge validates that your level matches that of a genuine technical reference — someone who can mentor, arbitrate, and make sound versioning decisions under pressure.
You learned Git during training but don't yet have a professional project to show. Earning the badge — even at Proficient level — gives you tangible proof that you go beyond git push, and that matters in an early-career application.
Clients and teams you join want to know you can slot into their Git workflow without handholding. An Advanced or Expert badge on your profile cuts the qualification round short and backs up your day rate.
Where and how your Git & GitHub badge will help you day to day.
You drop the link to your Git & GitHub badge on your LinkedIn profile or in your cover letter. The recruiter sees a score of 78/100 at Advanced level and knows you can handle PRs, rebase, and Actions before the first call even happens.
You're going for a tech lead role and need to back up your case with something more than tenure. The badge's detailed report gives you concrete, dimension-by-dimension evidence to bring into your performance review conversation.
A head of engineering uses badge scores to shortlist DevOps candidates without being able to test them personally. Instead of trusting self-reported skill levels, they filter for Advanced and Expert scores and cut the pre-screening time in half.
You share your badge on the first client call to signal you'll integrate without friction into their GitHub workflow — branch protections, PR conventions, Actions pipelines — no ramp-up period required.
You take the badge before and after an intensive Git training. The score delta makes your progress concrete: you move from Proficient (score 54) to Advanced (score 73), with the report pinpointing exactly which areas — like Actions matrix builds — still have room to grow.
A CTO has the whole dev team take the badge to get an honest picture of where everyone stands. She discovers two senior engineers have gaps in Actions workflows while a junior turns out to be surprisingly strong on interactive rebase — and adjusts the training plan accordingly.
A few minutes to check you have everything you need.
At the end of your session you don't just get a score — here's everything that awaits you.
You get a precise score from 0 to 100 and an official proficiency level (Novice, Proficient, Advanced, Expert) that reflects your actual command of Git and GitHub — earned in a live oral exam, not a multiple-choice quiz.
Claude Opus analyzes your transcript and delivers structured written feedback across all 5 scoring dimensions: Git mastery, GitHub collaboration, CI/CD automation, technical judgment, and communication. You know exactly where you shine and what to work on next.
Your oral session is securely stored and stays private. You can replay it to self-assess, spot where you hesitated, and sharpen your answers for a retake — or as prep for a real technical interview on Git topics like bisect or rerere.
You get a public URL linking to your Git & GitHub badge page with your score, level, and a summary of your strengths. Share it on LinkedIn, in a GitHub profile README, on your resume, or directly in a job application for verifiable proof of your skill level.
Discover related skills you can validate with Plume.
A 15-min oral exam with an AI, a shareable badge for your recruiters.
Choose this badge · €19.99
