Claude Code Course With Four Verified Repository Lessons

Complete one bounded repository change and hand off the tested diff, verification evidence, risks and rollback path.

4 lessons

Start free lesson

Who this course is for

Developers who can run a project locally but are new to coding agents.
Technical writers or product engineers who need a controlled first Claude Code workflow.

What you will be able to do

Prepare a repository and define a reversible change with expected behavior.
Use Plan Mode and narrow permissions before allowing edits.
Add tests, run project checks and inspect the exact diff.
Package the result with risks, rollback and reviewer notes.

Before you start

Basic familiarity with a terminal, version control and the project's test command.
A disposable practice repository or a branch whose current changes are understood.

View all 4 lessons

Prepare a bounded repository task
Inspect and plan with narrow permissions
Implement from tests and review the diff
Hand off evidence and a rollback

Understand the idea

Claude Code works inside a real repository, so unclear scope can affect more than the requested function. The task contract names the behavior, source of truth, allowed area, test command and stop condition before the agent reads or edits files.

Example

A TypeScript helper currently returns owner or Unknown. The product rule also treats whitespace-only names as blank but preserves the spacing in a nonblank name. Write expected outputs for undefined, an empty string, three spaces and a spaced name such as Maya before asking for code.

Write the change contract

Use the formatOwner case or another small practice issue. Record the current expression, four input-output pairs, the one helper and test file allowed to change, the project's real test and typecheck commands, the reviewer and a reversible starting point. Mark unrelated dependency and formatting changes out of scope. The deliverable is a change contract, not a patch.

Try this prompt

Turn this issue into a repository change contract: [issue]. Return current behavior expected cases allowed files forbidden changes verification commands reviewer stop conditions and rollback. Do not propose implementation yet.

Check your understanding

Keep in mind

Four inputs and expected outputs are written before editing
Allowed files and checks are named
A rollback point is recorded without discarding other work

Understand the idea

Plan Mode separates repository discovery from execution. The useful plan names exact files, existing conventions, tests and uncertainties; it should not hide unrelated cleanup inside the change.

Example

A useful plan names the helper and its existing test file, explains why a whitespace-only string passes the old truthiness check, proposes one conditional change and identifies the documented test command. A plan to update dependencies or reformat a directory fails the scope review.

Review a proposed plan

Open the practice repository in Plan Mode, or review a written plan without running Claude Code. Make an allow, ask or reject decision for each file and command. Require a reason for any network call or write outside the two exercise files. The output is an approved file-and-command list with unanswered questions, not a blanket approval.

Try this prompt

Inspect this repository for the contracted change. Do not edit. Return relevant files current tests smallest implementation plan commands requiring approval and open questions. Exclude unrelated cleanup.

Check your understanding

Keep in mind

A read-only plan identifies the exact files
Each proposed command receives a scope decision
Unrelated cleanup becomes a separate task

Understand the idea

Passing output is only one signal. Review the diff, changed files, command exit status and whether the implementation preserves behavior outside the new cases.

Example

The original helper passes undefined and empty-string tests but fails the whitespace case. A patch that returns owner.trim() fixes whitespace yet breaks the spaced-name case. The corrected expression tests owner?.trim() for emptiness and returns the original owner when nonblank.

Run the fixed regression set

Add assertions for undefined, empty, three spaces and a spaced name. Capture the original failing whitespace assertion, then rerun all four after the smallest fix. Run the repository's documented broader tests and typecheck, record exit codes, and inspect the exact diff for changed files, dependencies, generated output and secrets. The deliverable is a result table with pass, fail or not run for every check.

Try this prompt

Implement only the approved plan. Add the expected cases first, make the smallest change, run the repository's documented checks and return changed files command results and remaining risks. Do not delete or weaken tests.

Check your understanding

Keep in mind

The baseline failure is recorded
All four cases pass after the fix
Broader checks and the exact diff are reviewed

Understand the idea

A chat transcript is not a release record. The handoff needs scope, changed files, test evidence, known gaps, reviewer decision and the exact rollback point.

Example

A usable packet says that only formatOwner and its test changed; the baseline failed on whitespace; four cases now pass; the project test and typecheck commands and exit codes are attached; and the reviewer knows whether any check was skipped. It names the pre-change commit or branch and does not claim deployment.

Build the change packet

Write a handoff with the request, approved scope, changed files, before-and-after behavior, commands and exit codes, manual review, unresolved risks, reviewer decision and exact rollback point. Ask another person to reproduce the checks. If they cannot, correct the packet before treating the change as accepted.

Try this prompt

Turn this completed repository session into a change packet: [record]. Return request scope changed files behavior evidence commands with exit status manual checks unresolved risks reviewer decision and rollback. Do not claim a check that did not run.

Check your understanding

Keep in mind

Evidence is reproducible by another reviewer
Missing checks remain visible
Rollback names an exact point without touching unrelated changes

Frequently asked questions

Is the full course available on this page?

Yes. All four lessons, exercises, prompts and knowledge checks are available on the web.

Do I need a paid Claude plan?

Claude Code access and billing depend on the current Anthropic plan or API setup. Check the official access page before starting; the written exercises can be planned without sending code.

Does the course teach autonomous production deployment?

No. It teaches a bounded local change with human approval, tests, diff review and an explicit rollback.

Is this the official Anthropic Claude Code 101 course?

No. This is a WexAI practice course. Anthropic offers its own separate Claude Code 101 course through the official Anthropic Courses catalog.

Search WexAI

Claude Code Course With Four Verified Repository Lessons

Who this course is for

What you will be able to do

Before you start

Prepare a bounded repository task

Understand the idea

Example

Write the change contract

Try this prompt

Check your understanding

Keep in mind

Inspect and plan with narrow permissions

Understand the idea

Example

Review a proposed plan

Try this prompt

Check your understanding

Keep in mind

Implement from tests and review the diff

Understand the idea

Example

Run the fixed regression set

Try this prompt

Check your understanding

Keep in mind

Hand off evidence and a rollback

Understand the idea

Example

Build the change packet

Try this prompt

Check your understanding

Keep in mind

Frequently asked questions

Analytics

Who this course is for

What you will be able to do

Before you start

Understand the idea

Example

Write the change contract

Try this prompt

Check your understanding

Keep in mind

Understand the idea

Example

Review a proposed plan

Try this prompt

Check your understanding

Keep in mind

Understand the idea

Example

Run the fixed regression set

Try this prompt

Check your understanding

Keep in mind

Understand the idea

Example

Build the change packet

Try this prompt

Check your understanding

Keep in mind

Frequently asked questions

Keep learning & practicing

Read next

Apply the skill