recall

Extract action lines from commit history and generate structured development briefings grouped by scope.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mistakenot/auto-stack --skill recall-mistakenot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/mistakenot/auto-stack/tree/main/.agents/skills/recall
Command: npx skills add https://github.com/mistakenot/auto-stack --skill recall-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconstruct and narrate the current development context from contextual commits. Run at session start, when resuming work, or when switching branches. Produces a brief, conversational summary of where things stand.

Core Features & Use Cases

  • Extract contextual action lines from commit bodies (intent, decision, constraint, learned, rejected) and summarize them into a dense briefing.
  • Synthesize output by grouping signals by scope and domain, highlighting active work, decisions, risks, and blockers.
  • Surface rejections and constraints prominently to prevent wasted explorations and inform next decisions.

Quick Start

Run recall at session start, when resuming work, or when switching branches to generate a concise development briefing.

Frequently Asked Questions about recall

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

FAQPage Schema
How do I generate a concise project briefing from commit history?

Generate a concise project briefing by analyzing commit history to extract action lines like intent, decision, and constraint, then grouping them by scope to summarize current priorities and blockers. It reconstructs contextual development state from your commits.

What is the best way to understand the current state of a project when switching branches?

Understanding the current state of a project when switching branches requires synthesizing commit history into a structured briefing. It surfaces active work, decisions, risks, and rejected approaches to quickly orient you to the new branch context.

How do I resume work on a project and quickly recall previous decisions and constraints?

Resume work and recall previous decisions by running an analysis on your commit history. It extracts and groups contextual signals such as learned, constraint, and rejected action lines to produce a dense summary of where things stand.

Can I surface rejected approaches and constraints from commit history to prevent wasted exploration?

Yes, surfacing rejected approaches and constraints from commit history prevents wasted explorations. The analysis extracts rejected action lines and groups them prominently in the briefing to inform your next decisions and avoid redundant paths.

When do I need to analyze contextual commits for a development briefing?

Analyze contextual commits for a development briefing when starting a session, resuming work, or switching branches. It extracts intent, decision, constraint, and learned signals to output a structured summary highlighting active work and blockers.