Repository navigation
feat: add pt-snap memory leak diagnostic skill - #104
Conversation
c89fd3b to
2405a57
Compare
codeasier
left a comment
There was a problem hiding this comment.
Cross-review found six verified issues: one high, four medium, and one low. The focused tests pass, but they only assert static substrings and do not cover these command and query semantics.
|
All six findings are addressed in 493372b (10 focused tests pass; black/ruff clean).
|
# Conflicts: # AGENTS.md # skills/AGENTS.md
# Conflicts: # AGENTS.md # skills/AGENTS.md # tests/AGENTS.md
📝 Description
pt-snap-memory-leakworkflow for read-only SnapshotDB leak and retention diagnosis.🔗 Related Issue
Fixes #103
🧪 Testing
Commands run:
pytest tests/test_memory_leak_skill.py tests/test_setup_skill.py(4 passed)black --check tests/test_memory_leak_skill.pyruff check tests/test_memory_leak_skill.pypython3 /Users/test1/.agents/skills/agents-docs/scripts/validate_agents.py .(22 files, 0 errors, 0 warnings)git diff --check✅ Checklist
Snapshot Runtime Provenance
Snapshot provenance decision: no-update
Snapshot provenance no-update reason: This PR changes only agent skill documentation, static contract tests, and AGENTS navigation; no files under
src/pt_snap_cli/snapshot/**changed.📸 Screenshots (if applicable)
Not applicable.
📋 Additional Notes
The workflow accepts existing SnapshotDB files only. It does not install packages, persist focus, deserialize pickle input, or treat end-of-trace survival as proof of a confirmed leak.