Chess Coach Deprecated
Finds the recurring habit behind why I lose at chess, not just the losing move.
Deprecated. No longer maintained or developed. The code and its tests stay as they are.I'm not working on it anymore. The code stays as it is, and nothing new is coming.
How to use it
Three ways in, and one thing worth knowing about the answers.
Three ways to use it, and one thing worth knowing about what it tells you.
- Wait for the weekly digest Arrives only if the games changed. A quiet week stays quiet.It messages me weekly, but only if I have actually played.
- Ask about specific games, any time A question in chat runs the same analysis over whichever games it names.I can ask about particular games whenever I want.
- Expect a different answer for one game than for several One game gets a mistake; a set gets a habit. Both are true and they are not the same question.Ask about one game and it names a mistake. Ask about many and it names a habit.
- Or just read the published report The current findings, with the moves behind each, on this site.The latest findings are on this site, with the moves that prove them.
Read the current report
The live output: the habits costing me rating across the scored games, the moves behind each, and what to practise. Weaknesses only so far, and the page says so.
The live result: the habits losing me games, the exact moves that show each one, and what to work on. It only covers what is going wrong, and admits that.
Built From a Username
The archive pull, the local database, installing the engine, scoring every game and publishing the report were all built and run without further input. Fetching is conditional and merges rather than appends, so a second run over unchanged months rewrites nothing at all. The one thing it could not do was decide what was worth measuring.
From just a username, it downloaded the games, set up a chess engine, went through every move and published a report, all without being told how. Running it again when nothing has changed does nothing at all, which is why it can sit on a timer.
Every Move Scored at Home
Nothing is sent anywhere to be scored: the engine runs locally, bounded so a run cannot take the machine, and it resumes at the exact half-move it was stopped at. The output is the gap between the best move and mine, per position: the raw material for a pattern rather than a verdict on one game.
The analysis happens on my own machine, and it picks up exactly where it left off if it gets interrupted. For each position it records the difference between the best move and the one I played, which is what makes a pattern visible.
Patterns, With the Receipts Checked
Aggregating before reading is what makes the answer a habit rather than an anecdote: the model is handed a table, never the games. Every finding has to cite specific scored moves; a citation that cannot be resolved is discarded, and a finding whose citations all fail is rejected rather than published unsupported.
It groups everything first, so what comes out is a habit rather than one bad game. Anything it says has to point at real moves, and if it cannot, that finding is thrown away rather than published.
Weekly, On Demand, and Published
A quiet week produces no message rather than a re-run of the same report, which is what keeps the weekly note worth opening. The same analysis answers a question typed in chat, scoped to whichever games were mentioned, and the current findings are published as a page with the moves behind each one.
If I have not played, it stays quiet instead of repeating itself. I can also ask it about specific games whenever I want, and the latest findings are on this site for anyone to read.