Receber por email
← Voltar para o catálogo

work-session-journaler

Generates a detailed summary of a development session by analyzing the session transcript. Can be invoked manually or automatically from hooks.

0estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add ccronca/dotfiles

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/work-session-journaler/svg)](https://www.skillteca.com.br/skills/work-session-journaler)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 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

Work Session Journaler

Instructions

This skill analyzes a Claude Code session transcript and generates an intelligent summary.

Input Methods

Method 1: Current Session (Manual)

  • When invoked during an active session, analyze the current conversation context

Method 2: Transcript File (Hook/Automated)

  • Read the transcript file path from the user's message
  • Expected format: "Analyze session transcript: /path/to/transcript.jsonl"
  • Parse the JSONL transcript file to extract messages and tool usage

Analysis Requirements

  1. Read the Transcript: Use the Read tool to load the transcript file (if path provided)
  2. Extract Key Information:
  3. User messages (extract text from both string and structured content)
  4. Tool calls (Edit, Write, Bash commands, etc.)
  5. Working directory (cwd)
  6. Session progression
  1. Analyze and Summarize:
  2. Main Focus: What was the primary goal/task?
  3. Work Accomplished: What specific changes were made?
  4. Problems Solved: What issues were addressed?
  5. Files Modified: Which files were edited/created?
  6. Git Operations: Commits, PRs, branches
  7. JIRA/Tickets: Any ticket references
  8. Tools Used: Key tools and their usage
  1. Generate Summary: Create a concise 2-3 paragraph narrative that tells the story of what happened in the session

Output Format

Return a JSON object with the following structure that will be used to create the session summary file:

{
  "summary": "Concise narrative summary (2-3 paragraphs)",
  "focus": "Main focus/theme of the session",
  "files_modified": ["file1.py", "file2.js"],
  "git_operations": ["commit", "push", "pr_create"],
  "jira_tickets": ["JIRA-123"],
  "tools_used": ["Bash", "Edit", "Read"],
  "working_directory": "/path/to/project"
}

Important Notes

  • Focus on what was accomplished and why, not how
  • Identify patterns and themes across the session
  • Extract meaningful context from the conversation flow
  • Be concise but informative
  • If invoked from a hook, the output will be captured and used to create the session summary file
Compartilhar X LinkedIn