summary

Aggregate journal entries into project health patterns for a chosen time range.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/brewpirate/acme-frontier-ai --skill summary-brewpirate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summary
Source: https://github.com/brewpirate/acme-frontier-ai/tree/main/catalog/projects/field-notes/skills/summary
Command: npx skills add https://github.com/brewpirate/acme-frontier-ai --skill summary-brewpirate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a pile of journal entries into a concise picture of what is happening across a project, helping you spot recurring blockers, churn-heavy files, useful tools, and velocity trends without reading every entry by hand.

Core Features & Use Cases

  • Activity Breakdown: Counts sessions by entry type so you can see how effort is distributed across work, bugs, refactors, reviews, and exploration.
  • Hot File Detection: Identifies the most frequently modified files to reveal churn hotspots and possible refactoring or test-coverage needs.
  • Recurring Pattern Analysis: Deduplicates blockers, insights, and "would do differently" notes to surface repeated problems and successful practices.
  • Health Signals: Computes simple quality indicators such as bug-fix ratio, workaround ratio, blocker-free sessions, and repeat blocker rate.
  • Use Case: Use this Skill after a sprint or weekly planning cycle to quickly summarize team health and decide where to focus next.

Quick Start

Ask the summary skill to analyze the journal for the selected time range and return activity, hot files, recurring blockers, insights, skills usage, and health signals.

Frequently Asked Questions about summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize project journal entries to find recurring blockers and velocity trends?

To summarize project journal entries, aggregate session histories over a chosen time range to deduplicate blockers, rank modified files, and compute health signals like bug-fix ratio and repeat blocker rate. This reveals recurring blockers and velocity trends without manual review.

What are project health signals and how do I compute them from journal history?

Project health signals are simple quality indicators computed from journal history, including bug-fix ratio, workaround ratio, blocker-free sessions, and repeat blocker rate. They are calculated by counting activities and deduplicating blockers for a specific time range.

How can I identify churn hotspots and frequently modified files from work logs?

Identify churn hotspots by analyzing work logs to rank the most frequently modified files. This file detection highlights areas with high modification rates, signaling potential refactoring needs or test-coverage gaps within the project.

Can I use journal history analysis for sprint retrospectives and standups?

Yes, journal history analysis applies directly to retrospectives and standups. Aggregating entries breaks down activity distribution across work, bugs, and refactors, while surfacing repeated problems and successful practices for team discussion.

What is the best way to deduplicate recurring blockers and insights from session notes?

The best way to deduplicate recurring blockers and insights is to aggregate session notes across a time range, grouping identical issues and repeated successful practices. This surfaces unique recurring problems and consolidates insights for team health summaries.