automem-pending

Read pending AUTO-MEM entries and propose migrate-or-delete decisions for Wagner approval.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill automem-pending
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: automem-pending
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/automem-pending
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill automem-pending

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stale or missing documentation by forcing you to read pending AUTO-MEM entries and decide whether to migrate them into the canonical Git knowledge base or delete them when they are no longer needed.

Core Features & Use Cases

  • Auto-mem manifesto revalidation: Reads the AUTO-MEM-PENDING manifesto to confirm the suggested destination before touching the candidate auto-mem content.
  • Mandatory full auto-mem reading: Ensures the related auto-mem is read completely and not skipped to “just confirm”.
  • Decision proposal with guardrails: Proposes in one line whether to migrate to the indicated destination or delete, then waits for Wagner approval before executing.
  • Works across ERP modules and infra contexts: Triggers on reads/edits in key modules (e.g., NfeBrasil, Financeiro, Cms, Copiloto, Ponto), on session/business and UI navigation changes, and on deployment/SSH contexts.

Quick Start

When you are editing a relevant module or working in the specified paths, tell the AI: “Run automem-pending: detect the applicable AUTO-MEM candidates, read AUTO-MEM-PENDING.md and the full auto-mem, then propose migrate-to or delete, and ask for approval.”

Frequently Asked Questions about automem-pending

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

FAQPage Schema
How do I prevent stale or out-of-repo knowledge from accumulating in Git documentation?

To resolve pending AUTO-MEM entries during ERP module edits, you load AUTO-MEM-PENDING.md, read the full auto-mem candidate, and propose a single-line migrate-or-delete decision. You must wait for Wagner approval before executing any changes.

How do I migrate or delete pending AUTO-MEM entries in an ERP codebase?

To resolve pending AUTO-MEM entries during ERP module edits, you load AUTO-MEM-PENDING.md, read the full auto-mem candidate, and propose a single-line migrate-or-delete decision. You must wait for Wagner approval before executing any changes.

What is auto-mem drift and when does it happen across ERP modules?

Yes, auto-mem resolution triggers on session, business, and UI navigation changes, as well as deployment and SSH contexts. It specifically monitors key ERP modules including NfeBrasil, Financeiro, Cms, Copiloto, and Ponto.

Does auto-mem resolution work across deployment and SSH contexts or just module edits?

Yes, auto-mem resolution triggers on session, business, and UI navigation changes, as well as deployment and SSH contexts. It specifically monitors key ERP modules including NfeBrasil, Financeiro, Cms, Copiloto, and Ponto.

What are the limitations of skipping the full AUTO-MEM reading before confirming?

You must load the AUTO-MEM-PENDING.md manifesto, read the full related auto-mem entry, and propose a single-line migrate-to or delete decision. The workflow then waits for Wagner approval before executing the canonical Git knowledge base changes.