berserkdisruptors/contextual-commits/recall
Claude Code and agent skill by berserkdisruptors/contextual-commits
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install berserkdisruptors/contextual-commits/recallSKILL.md
Context Recall
Reconstruct the development story from contextual commit history and present it as a natural briefing.
Argument Detection
Check how recall was invoked:
- No arguments — run the default mode (full branch/session briefing below).
- Bare word (e.g.
recall auth) — treat as a scope query. Jump to Scope Query. - `word(word)` pattern (e.g.
recall rejected(auth)) — treat as an action+scope query. Jump to Action+Scope Query.
Default Mode (no arguments)
Step 1: Detect Branch State
Determine the working state:
DEFAULT_BRANCH identifies the repository's primary branch (for scenario C/D detection). BASE_BRANCH identifies the closest ancestor branch — which may differ when feature branches are created from non-default branches (e.g., a feature branched from develop). All branch-relative queries use BASE_BRANCH.
Step 2: Gather Raw Material
Scenario A — On a feature branch with commits
This is the richest scenario. Gather:
Scenario B — On a feature branch with no commits yet
Scenario C — On the default branch
Scenario D — On the default branch with uncommitted changes
Step 3: Extract Action Lines
From the gathered commit bodies, extract lines matching:
Group them by commit (preserve chronological order) and by type (for synthesis).
Step 4: Synthesize Output
Signal density over narrative flow. The output should be compact, scannable, and grounded entirely in what the commits and diffs show. Every line should be actionable information. No fluff, no conversational padding.
For Scenario A (branch with commits):
Output the branch state, then synthesize the contextual action lines into a dense briefing organized by what matters most for continuing work.
Example output:
When branched from a non-default branch:
Priority order:
- Active intent (what we're building and why)
- Current approach (decisions made)
- Rejected approaches (what NOT to re-explore — critical)
- Constraints (hard boundaries)
- Learnings (things that save time)
- In-progress work (unstaged/staged changes)
If intent evolved during the branch (a pivot), show both the original and current intent to make the pivot visible.
For Scenario B (branch with no commits):
For Scenario C (default branch, no changes):
Synthesize recent merged work from the last 20 commits. Group by area of activity. Surface any active constraints or learnings that apply broadly.
For Scenario D (default branch with uncommitted changes):
Same as Scenario C, with uncommitted changes noted at the top.
When there are no contextual commits at all
If the history contains conventional commits but no contextual action lines, still produce useful output from what exists:
This is honest about the signal quality while still providing useful orientation. The suggestion to adopt the skill is a natural next step, not a sales pitch.
Guidelines
- Dense over conversational. Every line should carry information. No "Here's what's been happening" or "Let me tell you about."
- Grounded in data. Only report what the action lines, commit subjects, and diffs actually show. Do not infer, speculate, or fill gaps.
- Surface rejections prominently. Rejected approaches are the highest-value signal — they prevent wasted exploration.
- Group by scope when multiple scopes exist. On the default branch with broad history, organize by domain area rather than chronologically.
- End with a prompt. Close with "What do you want to work on?" or similar. Keep it short.
- Scale to the data. If there are 2 contextual commits, the output is 3-4 lines. If there are 20, it's a few grouped paragraphs. Never pad thin data into a long output.
Scope Query (recall <scope>)
Targeted query across full repo history for a given scope. Prefix matching: auth matches auth, auth-tokens, auth-library, etc.
Step 1: Query
Step 2: Extract
From the gathered commit bodies, extract lines matching:
This captures all action lines whose scope starts with the query term.
Step 3: Output
Group by action type, chronological within each group. Show which sub-scopes were found.
Example (recall auth):
If no matches are found, say so plainly and suggest checking the scope name.
Action+Scope Query (recall <action>(<scope>))
Query a specific action type for a scope across full repo history.
Step 1: Query
Step 2: Extract
Step 3: Output
Flat chronological list with commit subject for provenance.
Example (recall rejected(auth)):
If no matches are found, say so plainly.
Proactive Usage
Before making a significant decision in any scope area, check rejected and constraint lines for that scope first:
If a previous commit recorded a rejected line for the approach you're about to propose, surface the rejection reason to the user before re-proposing it. The rejection may still stand, or circumstances may have changed — but the user should make that call with full context, not rediscover the same dead end.
Similarly, check constraint lines before proposing an approach that might violate a known boundary.
This check is lightweight and should become habitual for any scope you're actively working in.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/recall/SKILL.md
Popularity
- Repository stars
- 135
- Repository forks
- 2
- 7-day trend score
- 25
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 10 May 2026, 5 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/berserkdisruptors/contextual-commits/recall)