---
name: remind
description: Show the current state of a project — git status, structure, uncommitted work, recent activity, and saved context. Use when returning to a project after time away.
user-invocable: true
disable-model-invocation: false
context: fork
agent: Explore
allowed-tools: Bash, Read, Glob, Grep
argument-hint: "[optional: subdirectory to focus on]"
---

# Project State Reminder

Give a comprehensive but concise snapshot of the current project state.

## Pre-loaded context

### Git status
!`git status 2>/dev/null || echo "Not a git repository"`

### Current branch and all branches
!`git branch -a 2>/dev/null || echo "No git branches"`

### Recent commits (last 10)
!`git log --oneline -10 2>/dev/null || echo "No git history"`

### Top-level directory listing
!`ls -la`

### Remotes
!`git remote -v 2>/dev/null || echo "No remotes configured"`

## Your task

Using the pre-loaded context above, plus any additional reads you need, produce a structured project overview. If the user provided arguments, focus on that subdirectory: $ARGUMENTS

### Steps

1. **Read CLAUDE.md** (if it exists in the project root) — this has the project description, commands, and architecture
2. **Read MEMORY.md** (if it exists at `~/.claude/projects/*/memory/MEMORY.md` for this project, or `.claude/memory/MEMORY.md`) — this has non-obvious context from past conversations. If you find a MEMORY.md, also read any memory files it links to.
3. **Scan key files** — if the project has a README.md, package.json, Cargo.toml, pyproject.toml, requirements.txt, or similar, note their existence and what they reveal about the project

### Output format

Present a concise overview with these sections:

**What this project is** — 1-2 sentences from CLAUDE.md/README or inferred from structure

**Current branch & remotes** — branch name, tracking info, ahead/behind status

**Uncommitted changes** — modified files, untracked files/directories, staged changes. For each, briefly note what the change appears to be (e.g., "new dependency added" not just "modified requirements.txt")

**Recent activity** — summarize the last few commits in plain language (what was done, not just commit messages)

**Project structure** — key directories and their purpose, noting any that are large or notable

**Remembered context** — anything from MEMORY.md that's relevant (project goals, user role, ongoing work, decisions made)

Keep the whole output scannable — use short bullets, not paragraphs. The goal is to re-orient someone who hasn't looked at this project in a while.