check-gotchas

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Goal

Search the memory system for relevant gotchas, warnings, and learnings that apply to recent work. This is a proactive mistake-prevention check, not a git pre-commit hook.

By default, searches ALL accessible scopes (User → Project → Local) to ensure comprehensive gotcha coverage.

Execution Steps

1. Parse Arguments

Check for scope restriction:

• --scope user or --scope global → Search user scope only
• --scope project → Search project scope only
• --scope local → Search local scope only
• --scope enterprise → Search enterprise scope only (for managed environments)
• No --scope specified → Search ALL accessible scopes (recommended)

Note: --scope global is accepted as a legacy alias for --scope user.

Check for work scope (what to check):

• all or --all → Check all memories for gotchas (comprehensive review)
• staged → Check only staged git changes
• recent → Check recent work (last commit, uncommitted changes)
• {file-path} → Check specific file or pattern
• {topic} → Any other argument is treated as a topic to search for

If no arguments (default):

• Check recent work (uncommitted changes + last commit)
• If nothing recent, offer to check all gotchas

2. Determine Accessible Scopes

Check which scopes are accessible for searching:

# Check enterprise scope availability (for managed environments)
enterprise_enabled=$(memory config get scopes.enterprise.enabled 2>/dev/null | jq -r '.data // false')

# Check if in a git repo (for project/local scopes)
in_git_repo=$(git rev-parse --git-dir >/dev/null 2>&1 && echo "true" || echo "false")

Accessible scopes (in precedence order):

1. User - always accessible
2. Project - if in_git_repo is true
3. Local - if in_git_repo is true
4. Enterprise - if enterprise_enabled is true (for managed environments)

3. Load Gotcha Prevention Checklist Hubs