forget

Remove trigger phrases from .claude/triggers.json by file path or glob pattern.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/brewpirate/acme-frontier-ai --skill forget-brewpirate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forget
Source: https://github.com/brewpirate/acme-frontier-ai/tree/main/catalog/projects/total-recall/skills/forget
Command: npx skills add https://github.com/brewpirate/acme-frontier-ai --skill forget-brewpirate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes obsolete trigger phrases from the trigger index so you can keep recall data accurate and avoid stale matches.

Core Features & Use Cases

  • Targeted deletion: Removes entries by exact file path, glob pattern, or substring match.
  • Index maintenance: Updates .claude/triggers.json safely and reports exactly what was removed.
  • Use case: Use it when a file was renamed, deleted, or reworked and its stored trigger phrases should no longer fire.

Quick Start

Ask the forget skill to remove trigger phrases for the specified file or pattern from .claude/triggers.json and report the removed entries.

Frequently Asked Questions about forget

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

FAQPage Schema
How do I remove stale trigger phrases from a JSON index after renaming files?

To remove stale trigger phrases from a JSON index, you can delete entries by exact file path, glob pattern, or substring match. This updates the index safely and reports exactly what was removed.

What is the best way to delete obsolete model-specific triggers from a recall index?

Deleting obsolete model-specific triggers from a recall index involves targeted deletion using exact, glob, and substring matching across v1 and v2 entries. This approach keeps remaining index data accurate and provides clear removal guidance.

Can I use glob patterns to clean up broad path matches in a triggers JSON file?

Yes, you can use glob patterns to clean up broad path matches in a triggers JSON file. The process applies glob matching alongside exact and substring matching to safely remove unwanted entries and report the results.

When do I need to remove file-level triggers from my JSON index?

You need to remove file-level triggers from your JSON index when a file is renamed, deleted, or reworked. This prevents stored trigger phrases from firing and avoids stale matches in your recall data.

How to safely edit a JSON file to remove trigger entries without breaking the index?

To safely edit a JSON file and remove trigger entries without breaking the index, apply exact, glob, and substring matching to delete specific paths. The remaining index is kept accurate, and a removal report is generated.