Sample report

What a pattern report looks like

This is a static sample of the output GMSomeday is built to produce: repeated mistake patterns across a player's own games, named plainly, with one practice mission per leak.

Analyze my games Read the pattern story
Player sample
The Tension Releaser
Games scanned
22
●
●
●
●
●
●
●
●
Primary diagnosis

The recurring problem is not one blunder. It is a decision rule: when the center feels tense, this player trades first, simplifies the board, and gives away the imbalance that made the position playable.

  • Game 12: equal on move 19, lost after early central exchange
  • Game 17: winning on move 24, lost passive rook ending
  • Game 21: clean tactic missed after quiet queen move
Pattern stack

Three leaks, three missions

A useful report does not dump twenty engine lines on you. It names the repeated situation and gives you the next practice constraint.

Pattern 1

Releasing central tension too early

Showed up in 7 of the last 22 decisive games.

Trigger
Symmetrical pawn structures after an automatic d-pawn or e-pawn exchange.
Mission
Before exchanging central pawns, name what changes for both bishops and both rooks.
Pattern 2

Defending a worse endgame instead of changing the problem

Showed up in 4 games where the position was equal or better before move 25.

Trigger
A passive rook move after the opponent creates one queenside passer.
Mission
Find the active rook check or pawn break before adding a second defender.
Pattern 3

One-move tactic blindness after a safe-looking move

Showed up in 5 games, usually after a quiet improving move.

Trigger
Knight forks on c2, d3, f2, or g4 after moving the queen or rook.
Mission
Run a 10-second knight-fork scan before every quiet queen move.

The real report uses your games

This sample is deliberately static. The live report reads public games from Chess.com or Lichess and turns repeated positions into a short practice mission you can use before the next session.

Get my report