Recall — Development Context Briefing

What it does

• Detects the current branch and its real parent branch (via upstream or nearest-branch commit distance), plus staged/unstaged changes.
• Extracts contextual action lines from commit bodies: intent(...), decision(...), rejected(...), constraint(...), learned(...).
• Adapts output to four scenarios: feature branch with commits, feature branch without commits, default branch, and default branch with uncommitted work.
• Supports scope queries (recall auth, prefix-matching auth-tokens etc.) and action+scope queries (recall rejected(auth)) across all history.
• Falls back to a subject-line activity roundup when no contextual commits exist.

Who it's for

• Developers switching branches often and losing thread of what they were doing.
• Anyone resuming work after a break or picking up a teammate's branch.
• Teams tired of re-exploring approaches that were already rejected.

Examples

1. Run with no arguments at session start: get branch state, active intent, decisions, constraints, learnings and in-progress files in a few dense lines.
2. recall auth: grouped listing of every intent/decision/rejection/constraint/learning in the auth area, including sub-scopes.
3. recall rejected(payments): chronological list of discarded payment approaches with reasons and originating commit subjects, so you don't repropose a dead end.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/berserkdisruptors/contextual-commits/HEAD/skills/recall/SKILL.md

What I want: (describe your task here)

Install the skill I found on Claude Skill Mart.
Copy the skills/recall folder from the GitHub repo berserkdisruptors/contextual-commits into my ~/.claude/skills/recall/.
When it's done, tell me in one line what this skill can do.