Receber por email
← Voltar para o catálogo

analyze-history

Analyze past Claude Code conversation history for the current project to extract recurring errors, architectural decisions, lessons learned, and actionable recommendations. Use when the user asks about past sessions, wants to find repeated issues, review project evolution, or extract insights from conversation history.

0estrelas
Atualizado há 8 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add bikemazzell/claude-analyze-history

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/analyze-history/svg)](https://www.skillteca.com.br/skills/analyze-history)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Conversation History Analysis

Extract patterns, recurring errors, architectural decisions, and actionable recommendations from past Claude Code sessions for the current project.

When to Use

  • User asks about past conversations, patterns, or project history
  • User wants to find recurring errors or issues
  • User asks for a retrospective or lessons learned
  • User wants to know which areas of the codebase get the most churn
  • User asks "what have we done", "what keeps going wrong", "what sho

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn