agentleFS
Sign inStart free
star-gastar-ga/mind-mem/skills/apply-proposal/SKILL.md

apply-proposal

Skill22 starsChanged 6 months agoApache-2.0View on GitHub

Review and apply intelligence proposals generated by /scan. Uses atomic operations with rollback safety.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After /scan generates proposals in intelligence/proposed/

    line 6
  2. Distinctive:

    When proposals have been manually reviewed and approved

    line 8
  3. Distinctive:

    If any post-check fails, all changes roll back automatically

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/apply — Apply Proposals

Review and apply intelligence proposals generated by /scan. Uses atomic operations with rollback safety.

When to Use

  • After /scan generates proposals in intelligence/proposed/
  • During weekly triage sessions
  • When proposals have been manually reviewed and approved

How to Run

Dry Run (recommended first)

python3 maintenance/apply_engine.py P-20260213-001 "${MIND_MEM_WORKSPACE:-.}" --dry-run

Apply a Proposal

python3 maintenance/apply_engine.py P-20260213-001 "${MIND_MEM_WORKSPACE:-.}"

Rollback to Snapshot

python3 maintenance/apply_engine.py --rollback 20260213-143052 "${MIND_MEM_WORKSPACE:-.}"

Safety Protocol

  1. Always dry-run first — See what would change before applying
  2. Engine takes a state snapshot before any mutations
  3. If any post-check fails, all changes roll back automatically
  4. Applied proposals produce a receipt in intelligence/applied/<timestamp>/APPLY_RECEIPT.md
  5. Rejected proposals are marked with reason

Proposal Types

  • DECISIONS_PROPOSED.md — New decisions to formalize
  • TASKS_PROPOSED.md — New tasks to create
  • EDITS_PROPOSED.md — Edits to existing blocks (supersede, status change)

Triage Actions

  • ACCEPT — Apply the proposal
  • DEFER — Revisit later (stays in proposed)
  • REJECT — Dismiss with reason

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free