Repository Foundations
You have joined a new project and need to create clean, reviewable snapshots.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
CURRICULUM // GIT
Git Citadel
Build a reliable version-control workflow, then recover when history goes wrong.
GI48 CHALLENGES · 3 LEVELS
FOUR-ZONE PATH
From first command to incident recovery.
Each zone turns reference material into an active scenario. You will choose commands, repair mistakes, predict outcomes, and assemble complete workflows.
Branch Labyrinth
Several features are moving at once and you must keep their histories under control.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
Remote Outpost
Your local work must safely synchronize with a remote team repository.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
Recovery Vault
A change went wrong. Inspect the evidence and restore the repository without losing useful work.
- 8 practical command rooms
- 1 multi-step boss workflow
- Immediate explanations and safety notes
PRACTICE DESIGN
Every zone teaches a different operational decision.
The multi-step sequences below are authored workflows, while individual command rooms link to the closest available command reference.
Repository Foundations
Create the first reviewable snapshot in a new repository.
Initialize first, inspect the working tree, stage the intended files, commit them, then verify the resulting history.
Boss incident
Prepare an existing project for a clean first commit without skipping identity and status checks. Confirm the author identity and working tree before committing, then inspect the exact snapshot that was created.
Read the complete field guide →Branch Labyrinth
Develop a feature on an isolated branch and return to the integration branch safely.
A clean status check precedes branch creation; the feature is staged and committed before leaving its branch.
Boss incident
Temporarily protect unfinished work, inspect another branch, then return and restore the original work. The unfinished changes are identified and stashed before leaving the feature branch, then restored only after returning to that same branch.
Read the complete field guide →Remote Outpost
Update a feature branch with the latest remote main branch before opening a review.
Confirm local state, fetch remote references, move to the feature branch, rebase it, and inspect the rewritten history.
Boss incident
Publish a rebased feature branch while protecting teammates from an unsafe force push. Fetch before rebasing, publish rewritten history with force-with-lease rather than force, then verify the local state.
Read the complete field guide →Recovery Vault
Undo a bad shared commit without rewriting the published branch.
Inspect the repository and target commit before creating a new revert commit, then confirm the working tree is clean.
Boss incident
Recover a commit that disappeared after an accidental history rewrite. Use the reflog to locate the lost object, inspect it, anchor it with a branch, switch to that branch, and verify the recovered history.
Read the complete field guide →HOW THIS WORLD WAS BUILT
Source-linked commands, explicitly authored workflows.
The complete command library is public and each field guide explains prerequisites, failure modes, verification, and safety boundaries. Source-linked does not mean a command was executed on every platform.
Open the public command library →