← all posts
§018 · BlogAI Tools

10 Claude Code Workflows Every Developer Should Know.

Most people use Claude Code for one thing and stop. These ten cover the work that actually eats a sprint.

8 min read

Workflows covered
10
from 1-2 typical
Setup cost
One CLAUDE.md
Per session
Best first workflow
Test backfill
Ad hoc

Almost everyone uses Claude Code the same way at first.

Paste a task, get some code, move on.

That is the smallest possible version of the tool.

The workflows that pay for themselves are the boring ones nobody demos.

Test backfill. Dependency upgrades. Log triage. Migration scripts.

§01 · The problem

Where the time actually goes.

  1. 01Using it only for greenfield code
  2. 02No CLAUDE.md, so context is re-explained daily
  3. 03Ignoring it for tests and migrations
  4. 04Never using it to read unfamiliar code
  5. 05No custom commands for repeat tasks
  6. 06Running it without scope boundaries

The highest return tasks are the ones your team keeps postponing, not the ones they enjoy.

§02 · The mechanism

The AI workflow.

  1. 01

    Backfill tests on untested modules

    Agentic AI
  2. 02

    Upgrade dependencies and fix breakage

    Agentic AI
  3. 03

    Explain unfamiliar code before you touch it

    Assistive
  4. 04

    Run migrations and codemods at scale

    Automation
  5. 05

    Triage logs and reproduce the bug

    AI Agent
  6. 06

    Generate docs and changelogs from diffs

    Generative AI
Agentic AI
Model plans and executes a multi-step task
Assistive
Model suggests, human stays in control
Automation
Deterministic. No model involved
AI Agent
Model extracts, classifies, matches, or routes
Generative AI
Model drafts something a human will edit

§03 · The difference

Before vs after.

BeforeAfter
Tests postponed indefinitelyTest coverage backfilled module by module
Dependency upgrades deferred for quartersUpgrades run as a scoped, reviewable task
Onboarding to old code takes a weekAgent explains the module before you edit
Codemods written by hand, applied nervouslyCodemod written, applied, and verified
Log triage starts with grep and guessworkAgent reproduces from the log and proposes a fix
Changelog written from memory at releaseChangelog generated from the actual diff

§04 · The measure

Time saved.

TaskBeforeWith AI
Test backfill per module1 day30 min
Dependency upgrade2 days2 hrs
Onboarding to legacy code1 week1 day
Release notes2 hrsAutomatic

Continue reading

Tell us what you’re building.

Share a few details about what you need, and we’ll get back to you with a quotation.