Gentritbiba History Context
gentritbiba-history-context is a Claude Code plugin for the Operate phase that finds which sessions edited specific files and retrieves that conversation context from file-based history.
by gentritbiba · github.com/gentritbiba/history-context
Search local Claude Code session history by file path to see which conversations touched a file and pull that context back into the current session.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install gentritbiba-history-context@gentritbiba/history-contextBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:gentritbiba/history-context") and the paste-ready config with skillselion.get_install_config("plugin:gentritbiba/history-context").
What it does
gentritbiba-history-context is a Claude Code plugin for builders who edit the same files across many agent sessions and forget what was decided last time. Instead of scrolling chat logs or guessing from git blame alone, you search history indexed from local session artifacts to list which sessions touched a given file and open the relevant conversation snippets. That closes the loop between disk state and agent reasoning—especially when only part of a change set was committed or when commit messages are thin. Solo operators juggling support fixes and feature work get a practical audit trail without standing up a separate notes system. Use it when you return to a module after a break; skip if you only use ephemeral chats with no local history or you already centralize decisions in an issue tracker with perfect file links.
Highlights
- File-based history search across Claude Code sessions (no cloud index required in the description)
- Answer which sessions edited a specific file path
- Retrieve conversation context tied to those edits
- Keywords span claude, history, sessions, files, search, retrieve, conversation
- Single-plugin bundle (pluginCount: 1) from gentritbiba/history-context
Why builders use it
You reopen a file Claude helped change but cannot find which session discussed the logic, so you risk redoing work or breaking hidden assumptions.
After install, you can search by file, list contributing sessions, and pull prior conversation context into your current fix or iteration.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is gentritbiba-history-context for?
Developers who use Claude Code on a long-lived repo and need to trace agent-driven edits back to the conversations that produced them.
When should I use gentritbiba-history-context?
Use it during Operate-phase iteration when you are debugging, refactoring, or onboarding yourself to a file and need prior session context without manual log digging.
How do I add gentritbiba-history-context to my agent?
Install the gentritbiba/history-context plugin via Claude Code’s plugin mechanism, ensure local session history paths are available as the repo documents, then invoke the plugin’s file search from Claude Code to query sessions by path.
Comments
Share how you use gentritbiba-history-context, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.