Session 6 — Claude Code & CI/CD — Applied AI (Advanced)

🧠 Builder of CLAUDE.md

The file CLAUDE.md is loaded automatically at the start of each session: this is the contextual brain of the project. Complete the guided template — the ready-to-use file generates right in real time. Reminder: aim for density , not the length (< 150 lines).

1. Project overview

Project Name Description in one sentence — what, for whom Technical stack — languages, frameworks, database

2. Agreements

Style & naming — one agreement per line Folder structure — optional

3. Common commands — accurate and copyable!

Testing Lint/format Launch locally Other commands — one per line, “title: command” format

4. Known traps (gotchas)

One trap per line — be specific, this is the most profitable section Explicit prohibitions — optional: “What Claude Code should never do”

📄 Generated file

⚠ The constructor is a scaffolding : the final version requires a manual densification pass. Quality test: if this file could describe any project, it does not describe yours.

🏭 CI/CD pipeline designer

Build the flow visually PR → Review Claude Code → Testing → Deployment . Click on a step to configure it. Reminder of the golden rule: in mode headless (claude -p ), no one clicks “allow” — all permissions must be decided in advance.

👆 Click on a pipeline stage to configure it.

📄 Generated workflow (GitHub Actions skeleton)

⚠ Installation commands and exact flag syntax change with versions of Claude Code — check the official documentation today. There architectural logic (headless, pre-calibrated permissions, non-blocking, timeout) is stable.

🔒 Permissions configurator

Choose the regime of each integrated tool: Allow (authorized without confirmation), Ask (interactive confirmation — headless refusal), Deny (prohibited, priority over everything). THE .claude/settings.json is generated directly. Mental model: 🟢 free reading · 🟠 monitored writing · 🔴 locked execution.

Scenario Presets

Integrated Tools Catalog (Chapter 13)

Tool	Function	Risk	Diet

Bash patterns allowed — one per line, e.g. npm test:* Or git diff:* (active if Bash ≠ Deny) Reasons explicitly refused — one per line, e.g. Bash(rm:*) — the deny always wins

📄 .claude/settings.json

⚠ The exact syntax of the settings file changes depending on the version — check the official documentation. The logic allow explicit / priority deny / patterns by prefix is what is tested in certification.