Chess.com or Lichess.org? Turn your game history into a MoveForge training workflow
Some of your best training positions already exist — you played them in your own games. Here is how to move from Chess.com or Lichess.org history to analysis and useful MoveForge training material.
You already own a database of training positions. It is called your game history.
You can solve hundreds of random puzzles and watch dozens of other players' analyses. That has value. But there is another source of training material that nobody can tailor to you better than your own games.
That is where the positions live in which you genuinely hesitated. Openings where your memory suddenly ended. Tactics you failed to notice. Endgames where the plan looked good for five moves and then everything collapsed.
That is why MoveForge Game History becomes more useful when it is more than an archive of results. Take one of your Chess.com or Lichess.org games and ask a simple question:
“What can I take from this game into my next training session?”
Chess.com and Lichess.org — two sources, one process
If you play on Chess.com, work with your Chess.com games. If you play on Lichess.org, use your Lichess.org games. If you use both platforms, even better — you have more of your own material to compare.
Inside MoveForge, the important part is what happens after the game is available. You do not need two completely different learning systems.
The source changes where the game comes from. It does not change the question you ask after the game.
You want to know:
- where you first felt unsure about what to do,
- where the character of the position changed,
- whether the problem was tactical, positional or connected to your decision process,
- and whether the position is worth using again in training.
Step 1. Open Game History and start with your username
The simplest workflow does not begin with manually rebuilding an entire game move by move. In Game History, choose the source and work with publicly available games connected to a player's username.
This matters for training too. Instead of choosing a random position from the internet, you start with a game you actually played and decisions you may still remember.
If the game is fresh, try to remember before opening it:
- which moment felt hardest,
- where you spent a lot of time,
- which opponent move surprised you,
- and when you first thought that something might have gone wrong.
Those memories become useful reference points when you later compare your thinking with computer analysis.
Step 2. Do not analyze everything. Narrow the history to what matters.
If you play regularly, your history grows quickly. Trying to review every game in exactly the same way is a great way to turn analysis into homework.
MoveForge lets you narrow your history by factors such as time control, result and opponent. That means you can replace a huge list with a specific training question.
Examples:
- Rapid: I want games where I genuinely had time to think.
- Losses: I want to look for a recurring problem.
- One opponent: I want to see what keeps happening in our games.
- Blitz: I want to check which mistakes return when I play faster.
A filter is not just an interface convenience. Used well, it turns game history into a small database of your own training cases.
If you mainly play on Chess.com
Start with a handful of recent games from one time control. Do not mix Bullet, Blitz and Rapid immediately.
If your goal is better decision quality, begin with games where you had enough time to evaluate the position.
Later compare them with faster games and look for problems shared by both.
If you mainly play on Lichess.org
Use the same principle: a small group of games and one training question.
The platform logo is not what matters. The pattern in your decisions does.
If the same problem appears in several games, that is a stronger signal than one red badge in one review.
Step 3. Choose a game where the result does not tell the full story
Do not automatically open your biggest loss. A 0–1 result does not mean the entire game was bad. A 1–0 result does not prove that you played well.
The most useful games often include situations where:
- you were doing well for a long time but failed to convert the advantage,
- you won only after the opponent dropped material even though you had earlier problems,
- the opening was playable but you had no idea what plan to choose,
- one move turned a calm position into tactical chaos,
- or the result looks normal but you remember feeling unsure for half the game.
Those games reveal not only what you played but how you make decisions.
Step 4. Open the game and return to the position, not just the result
Once you choose a game, the board and move history become more important than the final score.
Replay the game and pause where you remember uncertainty. If you focus only on the result or the final evaluation, you can easily miss the origin of the problem.
Useful analysis often begins earlier.
Imagine that you lose a piece on move 24. The mistake itself may be obvious. But perhaps five moves earlier you placed every piece so passively that every later decision became difficult. In that case move 24 is the symptom, not the cause.
That is why Board Lab is useful not only for the moment everything collapses, but also for the position that led there.
Step 5. Ask your own question before revealing the engine answer
Before Stockfish shows a line, describe the problem in your own words.
For example:
- “I did not know where the queen belonged.”
- “I avoided the trade because I thought the ending would be bad.”
- “I assumed the opponent had to defend, so I never checked the counterattack.”
- “I focused on winning a pawn and ignored king safety.”
Only then compare your evaluation with the analysis.
If the engine suggests a move you never considered, do not memorize it mechanically. Follow the continuation and find the idea. The idea is what may return in another game.
Step 6. One game tells you something about a mistake. Several games tell you something about your habits.
This is where Game History becomes genuinely interesting.
If you miss a fork once, fine. Chess happens.
But if three of your last five games include the same issue:
- you did not check the opponent's threat,
- you left a piece undefended,
- you entered an ending without a plan,
- or you damaged a good position with one very fast move,
then you are no longer looking at an isolated accident. You are looking at a training theme.
That is why it is useful to revisit history in groups. Not to collect accuracy percentages, but to see whether the same problems keep coming back.
Step 7. Take the position out of history and give it a second life
The worst ending for a good analysis is closing the tab and forgetting everything the next day.
If you found a position with one important decision, use it again. In MoveForge you can work with the position in Board Lab, and material worth replaying can become another training position in Tactical Forge.
The role of game history changes:
Chess.com / Lichess.org → Game History → critical position → analysis → another training attempt.
That is more useful than viewing the answer once. A few days later the question is no longer: “do you remember what the engine showed?”
The question becomes: “can you find the right idea yourself now?”
What if a very recent game is not visible yet?
MoveForge Game History works with data made available by external chess services. A newly finished game therefore does not have to become available to every external tool at the exact moment you leave the board on Chess.com or Lichess.org.
Do not immediately assume something is broken. Try again later or review an older game in the meantime.
From a training perspective, that is not a bad habit either. Consistently reviewing a few useful examples matters more than repeatedly refreshing one game that has just ended.
Public games, not access to your private account
The Game History workflow is based on publicly available game data. A username and game source are enough to find the training material used in this process.
This distinction matters: MoveForge does not need private messages or game chat to give you the board, moves and material needed for post-game analysis.
For training, the game record is what matters. The rest is outside this workflow.
A 20-minute session
3 min: choose the source and narrow the history.
2 min: find one game with an interesting moment.
10 min: replay the critical positions and only then check the analysis.
5 min: write down one recurring issue or prepare a position for another training session.
A weekly session
Take 5–10 games from one time control and do not review every move equally.
Look for recurring patterns.
If three games point to the same problem, you have a ready-made theme for the next week of training.
You do not necessarily need more games. You need to use the games you already played better.
Chess.com and Lichess.org can give you hundreds of additional games. The number alone will not fix anything.
The value appears when history stops being a list of results.
Choose a game. Return to the decision. Find the cause. Check the analysis. Compare the problem with other games. Keep the best position for another training attempt.
Then a lost game is not wasted. It becomes material for the next session.