Pro Workflow
Corrections normally vanish when context compacts — you re-explain conventions every session.
Self-correcting memory system for Claude Code on a single SQLite store: every correction becomes an FTS5-searchable rule auto-loaded at session start, plus persistent research wikis that can grow via an auto-research loop. Ships 34 skills, 8 agents, 22 commands, and 37 hook scripts; also installable in Cursor, Codex, and 30+ other agents via SkillKit.
- Capture every correction so Claude never repeats the same mistake
- Build persistent rules that auto-load at the start of each session
- Run parallel development tasks across isolated workspaces
Corrections normally vanish when context compacts — you re-explain conventions every session. Pro Workflow persists every correction as a rule in SQLite and auto-loads it on session start, so the correction rate drops toward zero over time. 34 skills, 8 agents, 22 commands, 37 hooks.
Developers who repeatedly correct Claude on the same issues and want those corrections to persist and compound across sessions.
https://github.com/rohitg00/pro-workflow
By rohitg00
How to Get It
This is a methodology or approach. Paste the instructions below into a Claude conversation to get started.
/plugin marketplace add rohitg00/pro-workflow /plugin install pro-workflow@pro-workflow
After installing, paste this into Claude:
Help me capture every correction so Claude never repeats the same mistake
Trust Signals Reviewed
Community Pulse Active
Discussed on Hacker News, Reddit
- Apple debuts M5 Pro and M5 Max to supercharge the most demanding pro workflows — Reddit · 566 pts
- Apple debuts M5 Pro and M5 Max to supercharge the most demanding pro workflows — Reddit · 262 pts
- Apple debuts M5 Pro and M5 Max to supercharge the most demanding pro workflows — Reddit · 245 pts
3 mentions across 1 sources
Reviewer notes
Reviewed review. These are observations, not a security certification.
Compounding-corrections concept is genuinely useful. Same author as awesome-claude-code-toolkit.
Things to check
- Requires initial setup and correction history to build effective rules; may persist incorrect patterns if early corrections are flawed. SQLite backend could become a bottleneck with very large correction datasets across teams.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Compounding-corrections concept is genuinely useful. Same author as awesome-claude-code-toolkit.