claude-reflect vs pro-workflow
Claude Code plugin that learns from your corrections — hooks capture them in-session, /reflect syncs approved learnings to CLAUDE.md/AGENTS.md, /reflect-skills mines history into reusable commands. — versus — One SQLite store under every Claude Code session: corrections become FTS5-searchable rules that auto-load, research grows persistent wikis, and 37 hook scripts add quality gates.
Same core job — corrections that stick across Claude Code sessions. claude-reflect is the focused plugin (corrections → CLAUDE.md); pro-workflow builds a whole SQLite-backed memory-and-hooks platform around the idea.
| claude-reflect | pro-workflow | |
|---|---|---|
| Stars | 1.3k | 2.6k |
| Forks | 109 | 253 |
| Language | Python | JavaScript |
| License | MIT | — |
| Last activity | 4 months ago | 4 days ago |
| Topics | coding, memory | coding, memory |
| Curated connections | 9 | 4 |
claude-reflect — the curator's take
Install claude-reflect the third time you catch yourself typing the same correction into Claude Code. It's the pragmatic take on agent memory: no vector DB, no service — hooks queue corrections, you review, markdown files get smarter, and the AGENTS.md sync means Codex/Cursor/Aider benefit too. The /reflect-skills pattern-mining is the sleeper feature: 15 similar requests become one command. When NOT: if you expect actual memory infrastructure (semantic recall, knowledge graphs) — this is disciplined note-taking with AI triage, personal-scale by design. Everything lands via human review, which is a feature, not friction.
pro-workflow — the curator's take
The most complete attack on Claude Code amnesia we've mapped: correct it once and the correction becomes a durable, searchable rule; research lands in wikis that persist and even grow via an auto-research loop; hooks add git/secret guards and cost tracking. After 50 sessions the compounding is real. Two cautions: NO license file at review time (all rights reserved by default — same gap as this author's other tools), and 34 skills + 37 hooks is a lot of surface — adopt the memory core first, audit the hooks before letting them gate your commits.