cc-session-tools 3.1.0__tar.gz → 3.2.0__tar.gz

{cc_session_tools-3.1.0/src/cc_session_tools.egg-info → cc_session_tools-3.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cc-session-tools
-Version: 3.1.0
+Version: 3.2.0
 Summary: Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (hooks package)
 Author: raffishquartan
 License: MIT License
@@ -575,6 +575,10 @@ Curates the SHA-256 command cache the `bash-security-review` hook reads (`CCCS_U
 
 Archives (tar.gz, verified) then deletes `bash-security-review`'s own hook-security-check session transcripts — those whose first user message begins "Review this shell command for security risks" — which otherwise pile up by the thousands and pollute `claude --resume`/`--continue`. Triggers on "clean up hook sessions", "archive old hook security sessions", or `--resume` being cluttered with security-check conversations. Dry-run by default; 8-digit gated for `--execute` (via `generate-8digit-code`). Also runs unattended weekly via the bundled `clean-hook-sessions-weekly` job (see [Scheduled-task catch-up](#scheduled-task-catch-up)).
 
+### `compact-smart`
+
+Drafts the compaction-preservation paragraph you'd otherwise ask Claude for by hand before `/compact`, then hands back the exact `/compact <paragraph>` command to run — it never invokes `/compact` itself (Claude Code excludes that command from what a skill can invoke). Triggers on `/compact-smart`, "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session". Covers decisions and their rationale (especially mid-session corrections), file/PR/branch pointers, standing constraints, and outstanding tasks split into "Claude's next steps" vs. "the user's own to-dos" — then shows you the draft to confirm or edit (including dropping an unrelated thread) before finalizing. Refreshes the session's `working/WORKLOG.md` if one already exists (never creates one), which also clears the `worklog-guard` PreCompact hook's staleness gate for the command it hands back.
+
 See `docs/design.md` for the full design and CLI contract.
 
 ## Inter-session messaging

{cc_session_tools-3.1.0 → cc_session_tools-3.2.0}/README.md

@@ -518,6 +518,10 @@ Curates the SHA-256 command cache the `bash-security-review` hook reads (`CCCS_U
 
 Archives (tar.gz, verified) then deletes `bash-security-review`'s own hook-security-check session transcripts — those whose first user message begins "Review this shell command for security risks" — which otherwise pile up by the thousands and pollute `claude --resume`/`--continue`. Triggers on "clean up hook sessions", "archive old hook security sessions", or `--resume` being cluttered with security-check conversations. Dry-run by default; 8-digit gated for `--execute` (via `generate-8digit-code`). Also runs unattended weekly via the bundled `clean-hook-sessions-weekly` job (see [Scheduled-task catch-up](#scheduled-task-catch-up)).
 
+### `compact-smart`
+
+Drafts the compaction-preservation paragraph you'd otherwise ask Claude for by hand before `/compact`, then hands back the exact `/compact <paragraph>` command to run — it never invokes `/compact` itself (Claude Code excludes that command from what a skill can invoke). Triggers on `/compact-smart`, "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session". Covers decisions and their rationale (especially mid-session corrections), file/PR/branch pointers, standing constraints, and outstanding tasks split into "Claude's next steps" vs. "the user's own to-dos" — then shows you the draft to confirm or edit (including dropping an unrelated thread) before finalizing. Refreshes the session's `working/WORKLOG.md` if one already exists (never creates one), which also clears the `worklog-guard` PreCompact hook's staleness gate for the command it hands back.
+
 See `docs/design.md` for the full design and CLI contract.
 
 ## Inter-session messaging

{cc_session_tools-3.1.0 → cc_session_tools-3.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "cc-session-tools"
-version = "3.1.0"
+version = "3.2.0"
 description = "Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (hooks package)"
 readme = "README.md"
 license = { file = "LICENSE" }

cc_session_tools-3.2.0/src/cc_session_tools/skills/compact-smart/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: compact-smart
+description: Draft a compaction-preservation paragraph from the current session and hand back the exact /compact command to run - automates what the user otherwise asks for by hand ("give me a paragraph to pass to /compact"). Use when the user runs /compact-smart, or says "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session", "what should I tell compact to keep", or is about to /compact and wants to be sure nothing important gets lost.
+---
+
+# compact-smart
+
+Drafts the instructions `/compact [instructions]` should carry, then hands back the exact
+command to run. Does **not** invoke `/compact` itself - Claude Code's own docs explicitly
+exclude `/compact` from the set of built-in commands a skill can invoke, so the deliverable
+here is a ready-to-run command, not a compaction event.
+
+## Why this exists
+
+Real usage (a week of transcripts across every project) shows the user asking, by hand, for
+"a paragraph to pass to /compact" roughly 3 times for every bare `/compact` call - and
+re-explaining what counts as "relevant" nearly every time. What already survives compaction
+automatically (project-root `CLAUDE.md`, memory files, system/environment info) is re-loaded
+fresh from disk; what does **not** reliably survive is anything that only ever existed in
+the conversation itself - decisions, corrections, standing agreements, outstanding to-dos.
+A `/compact` instruction protects those for the *next* compaction only; the resulting
+summary is itself just conversation text again and can be trimmed by a *later* one - so this
+skill also refreshes the session's `WORKLOG.md`, if it has one, as a second, more durable
+safeguard.
+
+## What to draft
+
+Review the conversation so far (you already have it loaded - no need to re-read the
+transcript file from disk) and produce a paragraph covering, in this order:
+
+1. **Decisions and their rationale** - especially any point where the initial plan or
+   approach was found wrong and corrected mid-session. State the corrected approach and WHY
+   it changed, not just what the original plan was.
+2. **Concrete artifact pointers** - file paths, PR numbers, branch names, commit hashes,
+   OpenSpec change names, or anything else someone would need to go find the actual work.
+3. **Standing constraints or policies** established or confirmed during this session that
+   must carry forward (e.g. "no attribution lines in commits", "confirm before opening a
+   PR", a data-handling rule agreed mid-session). These are easy for a generic summary to
+   drop silently because they're usually stated once, early, and never repeated.
+4. **Outstanding tasks, split into two distinct groups**: what you (Claude) will do next,
+   and - separately and explicitly labeled - anything that is the *user's own* action to
+   take (e.g. "you still need to delete branch X yourself", "review the PR before merging").
+   Do not fold these two categories together.
+5. **An explicit "what happens next" statement.** Never leave this implicit.
+
+Keep it dense and concrete - file paths and specific facts, not vague summary language.
+
+## Handling `working/WORKLOG.md`
+
+Check whether the current session has one: `$CLD_SESSION_DIR/working/WORKLOG.md`.
+
+- **If it exists**: update it with the same substance as the draft above (append or rewrite
+  its "current state" section - match whatever structure the file already uses). This
+  repo's own `worklog-guard` PreCompact hook blocks a manual `/compact` if this file is more
+  than an hour stale, so refreshing it here also clears that gate for the command you're
+  about to hand back.
+- **If it does not exist**: do not create one. `ccd`/`ccr` never create a WORKLOG.md
+  automatically - it is opt-in scratch content the user or Claude may choose to keep during
+  a session, not mandatory state. Creating one here for the first time would be the skill
+  inventing a convention that has never applied to this session.
+
+## Confirmation step
+
+Show the drafted paragraph to the user before finalizing anything. Do not skip this even if
+the draft feels obviously complete - the point is to catch a miss before compaction discards
+the detail, not after. Accept:
+
+- Approval as-is, or
+- Free-form edits, or
+- An explicit exclusion ("drop the X thread, keep everything else") - a stale, unrelated
+  tangent that happened to occur in the same session is a real, recurring case; when asked,
+  remove that content from the paragraph rather than trying to talk the user out of it.
+
+This is a single review-and-edit round, not a multi-question interview - draft first, then
+let the user correct it in one pass. Asking a series of clarifying questions before drafting
+anything reintroduces exactly the friction this skill exists to remove.
+
+## Final output
+
+Once confirmed, present the exact command on its own line, ready to copy or type verbatim:
+
+```
+/compact <finalized paragraph>
+```
+
+Do not summarize what you're about to do instead of showing the literal command - the
+command itself is the deliverable.

{cc_session_tools-3.1.0 → cc_session_tools-3.2.0/src/cc_session_tools.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cc-session-tools
-Version: 3.1.0
+Version: 3.2.0
 Summary: Claude Code session management CLI tools (ccd, ccr, ccs, claude-code-usage, ccst) and hook library (hooks package)
 Author: raffishquartan
 License: MIT License
@@ -575,6 +575,10 @@ Curates the SHA-256 command cache the `bash-security-review` hook reads (`CCCS_U
 
 Archives (tar.gz, verified) then deletes `bash-security-review`'s own hook-security-check session transcripts — those whose first user message begins "Review this shell command for security risks" — which otherwise pile up by the thousands and pollute `claude --resume`/`--continue`. Triggers on "clean up hook sessions", "archive old hook security sessions", or `--resume` being cluttered with security-check conversations. Dry-run by default; 8-digit gated for `--execute` (via `generate-8digit-code`). Also runs unattended weekly via the bundled `clean-hook-sessions-weekly` job (see [Scheduled-task catch-up](#scheduled-task-catch-up)).
 
+### `compact-smart`
+
+Drafts the compaction-preservation paragraph you'd otherwise ask Claude for by hand before `/compact`, then hands back the exact `/compact <paragraph>` command to run — it never invokes `/compact` itself (Claude Code excludes that command from what a skill can invoke). Triggers on `/compact-smart`, "give me a paragraph to pass to compact", "draft a compact instruction", "help me compact this session". Covers decisions and their rationale (especially mid-session corrections), file/PR/branch pointers, standing constraints, and outstanding tasks split into "Claude's next steps" vs. "the user's own to-dos" — then shows you the draft to confirm or edit (including dropping an unrelated thread) before finalizing. Refreshes the session's `working/WORKLOG.md` if one already exists (never creates one), which also clears the `worklog-guard` PreCompact hook's staleness gate for the command it hands back.
+
 See `docs/design.md` for the full design and CLI contract.
 
 ## Inter-session messaging

{cc_session_tools-3.1.0 → cc_session_tools-3.2.0}/src/cc_session_tools.egg-info/SOURCES.txt

@@ -108,6 +108,7 @@ src/cc_session_tools/prompts/pdata-migration-skills-update.md
 src/cc_session_tools/skills/analyse-cc-usage/SKILL.md
 src/cc_session_tools/skills/clean-hook-sessions/SKILL.md
 src/cc_session_tools/skills/clean-hook-sessions/scripts/clean-hook-sessions.py
+src/cc_session_tools/skills/compact-smart/SKILL.md
 src/cc_session_tools/skills/context-override/SKILL.md
 src/cc_session_tools/skills/delete-sessions/SKILL.md
 src/cc_session_tools/skills/delete-sessions/scripts/delete_sessions.py

{cc_session_tools-3.1.0 → cc_session_tools-3.2.0}/tests/test_ccst_bundle_discovery.py

@@ -151,3 +151,15 @@ def test_pm_pdata_audit_and_migrate_are_bundled_skills():
     discovered = {p.name for p in ccst._discover_skills(ccst._discover_source_dir())}
     assert "pm-pdata-do-audit-and-prepare-to-migrate" in discovered
     assert "pm-pdata-do-migrate" in discovered
+
+
+def test_compact_smart_is_a_bundled_skill():
+    """compact-smart drafts a /compact preservation paragraph and hands back the exact
+    command to run - see openspec/changes/add-compact-smart-skill (archived) for the design.
+    Pure instruction skill, no backing script - this discovery assertion plus a frontmatter
+    sanity check is the extent of what's mechanically testable (design.md Decision 1)."""
+    skills = {p.name: p for p in ccst._discover_skills(ccst._discover_source_dir())}
+    assert "compact-smart" in skills
+    text = (skills["compact-smart"] / "SKILL.md").read_text()
+    assert text.startswith("---\nname: compact-smart\n")
+    assert "/compact-smart" in text