How to use the Code review checklist template

Start a board from it
Use this template opens a new Freero board with the Code review checklist template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Code review checklist”.
Follow the instruction on the board
“Agree the questions as a team, then keep them short enough to remember. Add an example from a real review to each so newcomers see why it matters.”
Fill in each part
- Does it do what the ticket asks, and nothing more?
- Would a test fail if this broke tomorrow?
- What happens with bad input, slow networks or empty lists?
- Can someone new understand it without asking?
- Is anything sensitive logged, stored or exposed?
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Code review checklist board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

Bug triage board
A kanban for incoming bugs, from new to fixed, with a severity guide everyone agrees on.
Bug bash plan
Organise an hour where everyone tries to break a feature before launch: scope, roles, test ideas, how to report and prizes.
Dependency upgrade board
Track library and framework upgrades from spotted to shipped, so security fixes and major versions don’t pile up.
Spike plan
Time-box a technical investigation: the question to answer, what’s in and out, the timebox and what you’ll hand back.
Postmortem action tracker
Follow the fixes agreed in incident reviews through to done, so the same failure doesn’t come back next quarter.
Straw, sticks, bricks retro
Sort the team’s practices by how sturdy they are: flimsy ones that fall over, shaky ones that need work, solid ones to build on.