pg-archive-agent-notes
/pg-archive-agent-notes
Pilnuje notatek agenta w repozytorium: sprawdza nowe wpisy, archiwizuje lub usuwa nieaktualne i stosuje ustalone reguły.
- Autor
- JusticeSc ↗
- Repozytorium
- project-governance ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 09.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pilnuje notatek agenta w repozytorium: sprawdza nowe wpisy, archiwizuje lub usuwa nieaktualne i stosuje ustalone reguły.
Oryginalny opis (EN)
Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in this repository; checks every new note for superseded active records, deletes records only about small UI or purely mechanical changes, classifies other implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind} triplet and manifest rules.
Jak działa
- Read the contracts
- Check supersession when adding a note
- Classify by future value
- Calibrated examples
- Archive one implemented triplet
- Validate and report
Podgląd SKILL.md
---
name: pg-archive-agent-notes
description: Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in this repository; checks every new note for superseded active records, deletes records only about small UI or purely mechanical changes, classifies other implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind} triplet and manifest rules.
---
# Archive Agent Notes
Reduce the active decision corpus without erasing history that can still guide work. Judge every note semantically; word count and age are discovery aids, never archive criteria.
## Read the contracts
Read [the Agent Note rules](../../notes/README.md), [the archive instructions](../../notes/archived/AGENTS.md), and the applicable active lifecycle instructions before classifying. Use current code, configuration, package docs, generated catalogs, newer Agent Notes, and inbound links to establish whether a rationale still owns or constrains anything.
## Check supersession when adding a note
Before drafting, apply the [creation criteria](../../notes/README.md#when-to-write-one). Every new Agent Note triggers a scoped audit of active notes covering the same decision, mechanism, or rejected alternative. Classify each full or partial supersession while writing the new note: archive qualifying implemented triplets in the same PR, retain and cross-link partial supersessions or independently useful rationale, reject obsolete proposals, and delete rejected notes that no longer prevent a plausible mistake. Apply the Agent Note consolidation rule when the new owner absorbs every unique proposition; do not defer a known match to a later corpus audit.
## Classify by future value
Apply these lifecycle-specific outcomes:
- **Implemented — delete:** delete complete triplets that only describe small UI adjustments or purely mechanical changes, and repair or remove inbound links. Local bug fixes, performance changes, new capabilities, and substantive behavior or ownership decisions do not qualify merely because they are implemented. Apply this criterion before keep/archive classification.
- **Implemented — keep active:** retain a note when its rationale, alternatives, negative guarantees, durable/wire semantics, ownership boundary, security rule, or reintroduction condition is likely to guide a future change. Classify the decision, not the mechanics of its implementation: a mechanical rename or type extraction can still record lasting naming, compatibility, or ownership rules. Length does not matter.
- **Implemented — archive:** archive a substantive historical decision when it is complete and unlikely to guide future work, but its historical rationale still warrants preservation. Do not archive records that meet the direct-deletion criterion.
- **Proposed — never archive:** keep a live proposal active; if it is no longer worth pursuing, reject it with an honest reason and satisfy the rejected lifecycle format.
- **Rejected — keep only as a guardrail:** retain a rejection only when the losing proposal remains a tempting, meaningful mistake and the note explains why it loses.
- **Rejected — delete:** delete the whole triplet when the rejected idea is obsolete, superseded, no longer plausible, or unlikely to prevent re-litigation. Repair or delete inbound links.
Do not archive toward a quota. Inspect every note in scope, classify analogous groups under one principle, use best judgment for close cases, and record genuinely borderline decisions for the handoff.
## Calibrated examples
Size is not the test; decision value is.
Delete implemented notes such as:
- a one-line UI label adjustment — closed, minor presentation behavior;
- a completed function relocation with unchanged behavior.
Keep implemented notes such as:
- a validation rule that every future format change must preserve;
- a cross-workspace ownership or dependency-direction rule;
- a durable file-format or identity policy;
- a negative guarantee whose removal would look safe next quarter.
For rejected notes:
- keep a rejection whose losing proposal remains tempting and cheap to re-propose;
- delete a rejection whose premise no longer exists in the code or plan;
- delete a rejection that a newer decision already answers.
## Archive one implemented triplet
Sealing requires a Git-committed trusted baseline: the verifier compares each manifest entry with committed objects. In a checkout with no commits, the archive cannot establish that baseline; do not fabricate seals, hashes, or manifest entries to satisfy the command.
1. Move the complete `foo.md`, `foo.zh.md`, and `foo.i18n.yaml` triplet from `implemented/<kind>/` to `archived/<kind>/`; `implemented` is deliberately absent from the archive path.
2. Make no body edits. Insert only `Archived: YYYY-MM-DD` immediately below `Status: implemented` in both language files, using the archival date and the same value on both sides.
3. Re-record the sidecar hashes mechanically for the two metadata-only edits. Do not translate, reformat, update facts, or repair links inside the note. Existing title punctuation, blank-line layout, and language-switcher wording are preserved, not prerequisites for archival.
4. Search for inbound links from active prose. Redirect them to current authority, retarget them to the archived path only when the historical snapshot is intentionally cited, or delete them. Never verify or repair links out of the archived note.
5. Run `pnpm run verify-archived-agent-notes --write`. Its append-only mode first proves every existing seal still matches, then adds only the new triplet hashes. Run the normal verifier afterward.
After the triplet is sealed, never edit, move, translate, reformat, or delete it. Archived notes remain valid inbound-link targets but are historical snapshots, not authority for current behavior.
## Validate and report
Run the archive verifier's focused test, `pnpm run verify-archived-agent-notes`, `pnpm run doc-sync`, `pnpm run lint`, and `git diff --check`; select any additional evidence through [pg-pre-push-checks](../pg-pre-push-checks/SKILL.md).
Report active implemented notes kept, implemented notes deleted or archived, rejected notes kept/deleted, proposed notes rejected if any, and every genuinely borderline case with its word count and chosen outcome. Do not claim archived outbound links are valid: the archive verifier intentionally never checks them.
Wersje
W bazie nie ma innych skilli o nazwie pg-archive-agent-notes.
Migawka bazy z 13.11.2026 · wersja paczki 52e799ceda37 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100archive-agent-notes
Dodaje, sprawdza, odchudza i archiwizuje notatki agentów w projekcie, usuwając zastąpione rekordy i te czysto mechaniczne. - 100dsh-archive-agent-notes
Dodaje, audytuje, przycina, archiwizuje i przywraca Agent Notes w deepseek-harness, oceniając wartość każdej notatki dla przyszłych decyzji i stosując zamrożone reguły katalogu archived. - 100dsh-archive-agent-notes
Dodaje, audytuje, przycina, archiwizuje i przywraca Agent Notes w deepseek-harness, klasyfikując wdrożone notatki według wartości dla przyszłych decyzji. - 90agent-notes
Ustala, czy zmiana w Cherry Studio wymaga Agent Note, prowadzi specyfikacje i zapisuje trwałe decyzje o poprawkach błędów. - 90openspec-bulk-archive-change
Archiwizuje wiele zakończonych zmian OpenSpec naraz, rozwiązując konflikty specyfikacji według stanu kodu. - 100openspec-bulk-archive-change
Archiwizuje naraz kilka zakończonych zmian OpenSpec, gdy równoległe zmiany są gotowe do zamknięcia.