recall

Reconstruct development context from git commit history into structured intent and decision lines.

145|3|Updated Feb 27, 2026

Search Tags:#git #developer-workflow #commit-history #conventional-commits #decision-tracking #context-recall #branch-summary

Ready to run

npx skills add https://github.com/berserkdisruptors/contextual-commits --skill recall-berserkdisruptors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/berserkdisruptors/contextual-commits/tree/main/skills/recall
Command: npx skills add https://github.com/berserkdisruptors/contextual-commits --skill recall-berserkdisruptors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you recover the reasoning behind recent and historical code changes by reconstructing development context from contextual commit messages. It reduces repeated exploration, prevents revisiting rejected approaches, and makes branch handoffs or session resumes much faster.

Core Features & Use Cases

Branch Briefing: Summarizes the current branch state using commit intent, decisions, rejections, constraints, learnings, and any staged or unstaged work.
Targeted History Queries: Searches repository history by scope such as auth or by typed action such as rejected(auth) to find prior reasoning quickly.
Resume and Handoff Support: Useful at session start, when switching branches, or before making a major technical decision in an area with existing history.

Quick Start

Ask the AI to use the recall skill to summarize the current branch context or to look up prior decisions for a scope like auth.

Frequently Asked Questions about recall

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

FAQPage Schema

How do I recover development context from git commit history?▼

Recover development context from git commit history by reconstructing structured intent, decisions, rejections, constraints, and learnings from past commits. This reduces repeated exploration and prevents revisiting rejected approaches when switching branches.

How do I summarize a git branch before switching or handing it off?▼

Summarize a git branch by generating a briefing that extracts commit intent, decisions, rejections, constraints, learnings, and any staged or unstaged work. This provides a concise state overview for faster branch switching and session handoffs.

Can I search git history for prior decisions about a specific scope like auth?▼

Search git history for prior decisions by querying specific scopes or typed actions such as rejected(auth). This targeted history lookup finds prior reasoning quickly without manually reading through every commit message.

What are conventional commits and how do they help with decision tracking?▼

Conventional commits structure commit messages with typed actions and scopes, enabling automated decision tracking and contextual parsing. This format allows tools to extract intent, rejections, and constraints directly from the commit history.

Does this approach require a specific git workflow or commit message format?▼

This approach requires contextual commit messages containing structured intent, decisions, rejections, constraints, and learnings. It applies to standard git workflows using conventional commits, branch base detection, and diff awareness for accurate synthesis.

When should I not use automated commit history reconstruction?▼

Avoid automated commit history reconstruction when commits lack structured contextual messages or when the repository history is too shallow for meaningful synthesis. The tool relies entirely on observed commits and changes, so sparse history yields limited context.