Skip to content
Module
Module 5 of 5Lesson 2 of 3~20 min

Workshop: your way of working on your repository

The final workshop brings the course together in a concrete deliverable installed on your own repository: instructions, settings, guardrails, an extension and a review routine. You apply it to a real task and keep evidence that each piece works, so you can then work with Claude Code confidently on a project that matters.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this workshop, you will have installed on your own repository a reviewed CLAUDE.md, a .claude/settings.json with tested permissions and hooks, a useful extension (review subagent or command) and a review checklist, and applied them to a real task, with evidence.

Topics covered

  • Claude Code workshop
  • coding agent setup
  • CLAUDE.md
  • hooks and permissions
  • code review

Where it fits

Review, automate and deliver your set-up

How do I know the agent's work is good before it ships, and install the whole set-up on my repository?

Lessons in this module

  1. Review the agent's work, then automate it
  2. Workshop: your way of working on your repository (this lesson)
  3. Exit kit and application plan

What you will learn in this module

This lesson is part of the course Work with Claude Code on a real project: context, planning, review

  • Explain what fills Claude Code's context window and manage it (/context, /clear, /compact, resuming and naming sessions), taking cost into account.
  • Write a short, useful CLAUDE.md placed at the right level of the hierarchy (user, project, local, subdirectory, path-scoped rules), with imports if needed.
  • Run a task on existing code as explore, plan, code, commit, with plan mode, verification criteria and Git rather than checkpoints alone.
  • Choose and justify the right mechanism for a need (CLAUDE.md, skill or command, subagent, MCP server, hook) and set it up in the repository.
  • Choose a permission mode and write allow, ask and deny rules suited to the project's risks, in the right settings file.
  • Write simple hooks as deterministic guardrails (block, format, verify) and know their risks and limits.
  • Review the agent's work with a checklist (scope, tests, secrets, migrations, dependencies) and an independent review, and know when to automate it in non-interactive mode or in GitHub Actions.

Related courses