chronicle-context-retriever
Search Your Development History with Chronicle
Stop repeating past mistakes and rediscover solutions you have already implemented. This skill searches your Chronicle database to find relevant context from previous development sessions. Build on past work instead of starting from scratch.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "chronicle-context-retriever". What did I do yesterday regarding the authentication system?
Resultado esperado:
- Session #142 - Implemented JWT token validation
- Session #143 - Fixed login redirect issue
- Session #144 - Added password reset functionality
- Key decisions: Used Auth0 instead of custom solution
- Blockers: CORS issues with frontend integration
- Solutions: Added proper headers and proxy configuration
Auditoria de Segurança
SeguroThis skill is a pure documentation file (SKILL.md) with no executable code, network calls, or file system access. It only provides instructions for using existing Chronicle MCP tools and CLI commands. All 77 static findings are false positives triggered by the static analyzer misinterpreting documentation elements (markdown code backticks, example paths, and documentation terminology) as security threats.
Fatores de risco
🌐 Acesso à rede (1)
⚙️ Comandos externos (53)
📁 Acesso ao sistema de arquivos (1)
Pontuação de qualidade
O Que Você Pode Construir
Recall Past Implementations
Quickly find how you solved similar problems before, including decisions made and issues encountered.
Get Project Context
Understand what work was done while you were away, including recent decisions and current blockers.
Learn from Past Blockers
Identify what blocked progress previously and how it was resolved to avoid hitting the same issues again.
Tente Estes Prompts
Search my Chronicle sessions for work on authentication implementation in the last 2 weeks
What was the blocker we hit with the database migration and how did we solve it?
How did I implement the user-dashboard feature? Show me the approach and key decisions
Search for all sessions about API performance issues and summarize the common patterns
Melhores Práticas
- Start with broad searches to find relevant areas, then narrow down with specific terms
- Use both MCP tools for structured JSON output and CLI commands for portable access
- Review failed sessions too - they often contain valuable lessons about what to avoid
Evitar
- Do not rely solely on memory - search Chronicle first before reinventing solutions
- Avoid searching only for successful sessions - failed attempts often contain valuable lessons
- Do not skip the deep-dive phase after initial broad searches
Perguntas Frequentes
Do I need Chronicle installed to use this skill?
What is the difference between MCP and CLI approaches?
How far back can I search?
Is my session data safe?
What if MCP tools are not working?
Can I search other people is sessions?
Detalhes do Desenvolvedor
Autor
ChandlerHardyLicença
MIT
Repositório
https://github.com/ChandlerHardy/chronicle/tree/main/chronicle-skills/chronicle-context-retrieverReferência
main
Estrutura de arquivos
📄 SKILL.md