Problem
The installed research-git guidance tells agents that research-git is available and includes this recall instruction:
For recall/resurrection requests, use the rgit-recall skill.
However, in practice a user may ask for a previous idea or feature in natural language without explicitly mentioning research-git, rgit, recall, or tagging the capability. In that case, the agent may treat the request as an ordinary coding request and not realize that research-git recall should be used.
Examples of requests that may be missed:
- Bring back the old ranking experiment.
- Restore the previous cache idea we tried.
- Re-apply that earlier implementation to the current codebase.
- Use the version of this feature we explored before.
Current behavior
The recall ability exists through the rgit-recall skill, whose description covers recall/resurrection/bring-back requests. But if the agent does not connect the user wording to that skill, the user has to explicitly mention or tag research-git for the feature to be used.
Expected behavior
After research-git is installed, the agent should reliably recognize natural-language requests to bring back, restore, resurrect, re-apply, or reuse previously captured work as research-git recall opportunities, even when the user does not explicitly mention research-git.
Environment
- research-git version: 0.0.7
- Context: Codex / AGENTS.md managed guidance and installed
rgit-recall skill
Impact
Recall becomes much less discoverable than capture: users need to already know the feature exists and name it explicitly, instead of being able to ask naturally for prior work to be brought back.
Problem
The installed research-git guidance tells agents that research-git is available and includes this recall instruction:
However, in practice a user may ask for a previous idea or feature in natural language without explicitly mentioning
research-git,rgit,recall, or tagging the capability. In that case, the agent may treat the request as an ordinary coding request and not realize that research-git recall should be used.Examples of requests that may be missed:
Current behavior
The recall ability exists through the
rgit-recallskill, whose description covers recall/resurrection/bring-back requests. But if the agent does not connect the user wording to that skill, the user has to explicitly mention or tag research-git for the feature to be used.Expected behavior
After research-git is installed, the agent should reliably recognize natural-language requests to bring back, restore, resurrect, re-apply, or reuse previously captured work as research-git recall opportunities, even when the user does not explicitly mention research-git.
Environment
rgit-recallskillImpact
Recall becomes much less discoverable than capture: users need to already know the feature exists and name it explicitly, instead of being able to ask naturally for prior work to be brought back.