capt-hook 6.4.0__tar.gz → 6.5.0__tar.gz

capt_hook-6.5.0/PKG-INFO

@@ -0,0 +1,146 @@
+Metadata-Version: 2.4
+Name: capt-hook
+Version: 6.5.0
+Summary: Stop repeating yourself to Claude.
+Keywords: claude,claude-code,hooks,llm,agents,guardrails,cli
+Author: Yasyf Mohamedali
+Author-email: Yasyf Mohamedali <yasyfm@gmail.com>
+License-Expression: PolyForm-Noncommercial-1.0.0
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Dist: cc-transcript>=7.1,<8
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pydantic-settings>=2.0
+Requires-Dist: tree-sitter>=0.24
+Requires-Dist: tree-sitter-bash>=0.23
+Requires-Dist: ast-grep-py>=0.39,<1
+Requires-Dist: funcy>=2.0
+Requires-Dist: spacy>=3.7
+Requires-Dist: click>=8
+Requires-Dist: rich>=13
+Requires-Dist: orjsonl>=1.0
+Requires-Dist: wn>=1.1.0
+Requires-Dist: lazy-object-proxy>=1.12.0
+Requires-Dist: filelock>=3
+Requires-Dist: loguru>=0.7.3
+Requires-Dist: spawnllm>=0.5.2,<0.6
+Requires-Dist: pytest>=8.0 ; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.24 ; extra == 'dev'
+Requires-Dist: pyright>=1.1 ; extra == 'dev'
+Requires-Dist: pyyaml>=6 ; extra == 'dev'
+Requires-Dist: ruff>=0.8 ; extra == 'dev'
+Requires-Python: >=3.13
+Project-URL: Homepage, https://github.com/yasyf/captain-hook
+Project-URL: Documentation, https://yasyf.github.io/captain-hook/
+Project-URL: Repository, https://github.com/yasyf/captain-hook
+Project-URL: Issues, https://github.com/yasyf/captain-hook/issues
+Project-URL: Changelog, https://github.com/yasyf/captain-hook/blob/main/CHANGELOG.md
+Provides-Extra: dev
+Description-Content-Type: text/markdown
+
+# ![captain-hook](https://github.com/yasyf/captain-hook/raw/main/docs/assets/readme-banner.webp)
+
+**Stop repeating yourself to Claude.** captain-hook mines your transcripts for the corrections you keep giving and opens PRs that turn each one into a typed, tested Python hook.
+
+[![CI](https://github.com/yasyf/captain-hook/actions/workflows/ci.yml/badge.svg)](https://github.com/yasyf/captain-hook/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/capt-hook)](https://pypi.org/project/capt-hook/)
+[![License: PolyForm Noncommercial](https://img.shields.io/badge/license-PolyForm--Noncommercial--1.0.0-blue)](https://github.com/yasyf/captain-hook/blob/main/LICENSE)
+
+## Get started
+
+```bash
+uvx capt-hook init
+```
+
+`init` scaffolds `.claude/hooks/`, wires Claude Code's settings, and arms the session reviewer. One `block_command` later, a force-push dies at `PreToolUse` and the hook's inline tests run green:
+
+<img src="https://github.com/yasyf/captain-hook/raw/main/docs/assets/demo.png" alt="Terminal running 'uvx capt-hook test' — a hook blocks git push --force and both inline tests pass" width="700">
+
+Driving with an agent? Paste this:
+
+```text
+/plugin marketplace add yasyf/captain-hook
+/plugin install captain-hook@captain-hook
+```
+
+<details>
+<summary>Prefer a prompt over the plugin?</summary>
+
+```text
+Run `uvx capt-hook init` in this repo, write one hook that blocks force-pushes,
+and verify it with `uvx capt-hook test`. Read https://yasyf.github.io/captain-hook/
+if you get stuck.
+```
+
+</details>
+
+---
+
+## Use cases
+
+### Block force-push and rm -rf before they run
+
+One bad Bash call rewrites shared history or eats a directory, and by the time you spot it in the transcript it already ran. Declare the block once, tests inline:
+
+```python
+# .claude/hooks/safety.py
+from captain_hook import Allow, Block, Input, block_command
+
+block_command(
+    ["git", "push", "--force"],
+    reason="Force-pushing rewrites shared history",
+    hint="Use `git push --force-with-lease` instead",
+    tests={
+        Input(command="git push --force"): Block(),
+        Input(command="git push origin main"): Allow(),
+    },
+)
+```
+
+The next `git push --force` never executes: the agent sees `BLOCKED: Force-pushing rewrites shared history` plus the hint, and reaches for `--force-with-lease` instead. `rm -rf` is one more `block_command` away.
+
+### Turn repeated corrections into rules Claude can't forget
+
+You've typed "use uv, not pip" in a dozen sessions, and session thirteen makes the same mistake. After `init`, the session reviewer reads each transcript as the session ends, keeps the corrections that are standing rules, and — once a pattern proves itself across sessions — opens a PR that codifies it as a hook. Watch the pipeline:
+
+```bash
+uvx capt-hook status
+```
+
+The dashboard lists every correction it's tracking, staged from first sighting to open PR. You review the PR like any other; merged hooks enforce the rule from then on.
+
+### Gate "done" until the tests actually pass
+
+The agent declares victory while the suite is red. A Stop gate holds the line:
+
+```python
+# .claude/hooks/quality.py
+from captain_hook import RanCommand, TouchedFile, gate
+
+gate(
+    "You edited Python files but never ran the tests. Run `uv run pytest` before finishing.",
+    only_if=[TouchedFile("**/*.py")],
+    skip_if=[RanCommand(r"\bpytest\b")],
+)
+```
+
+The agent can't end the turn until a pytest run shows up in the transcript, and the gate stands down on its own once one does.
+
+## More in the docs
+
+- **Session reviewer** — the full corrections lifecycle, from transcript to merged hook PR — [guide](https://yasyf.github.io/captain-hook/docs/guide/session-reviewer.html)
+- **Conditions** — typed filters over tools, files, commands, and transcript history — [guide](https://yasyf.github.io/captain-hook/docs/guide/conditions.html)
+- **LLM hooks** — gate on a model's verdict when a regex can't decide — [guide](https://yasyf.github.io/captain-hook/docs/guide/llm-hooks.html)
+- **Workflows** — multi-step Stop gates with artifact checks and checklists — [guide](https://yasyf.github.io/captain-hook/docs/guide/workflows.html)
+- **Packs** — the shipped `general`, `python`, and `go` hook packs — [guide](https://yasyf.github.io/captain-hook/docs/guide/packs.html)
+- **Testing** — run `uvx capt-hook test --json` in CI so a regressed hook fails the build — [guide](https://yasyf.github.io/captain-hook/docs/guide/testing.html)
+
+Read the [docs](https://yasyf.github.io/captain-hook/) for the full guide. Licensed under [PolyForm Noncommercial 1.0.0](https://github.com/yasyf/captain-hook/blob/main/LICENSE), free for noncommercial use.

capt_hook-6.5.0/README.md

@@ -0,0 +1,98 @@
+# ![captain-hook](https://github.com/yasyf/captain-hook/raw/main/docs/assets/readme-banner.webp)
+
+**Stop repeating yourself to Claude.** captain-hook mines your transcripts for the corrections you keep giving and opens PRs that turn each one into a typed, tested Python hook.
+
+[![CI](https://github.com/yasyf/captain-hook/actions/workflows/ci.yml/badge.svg)](https://github.com/yasyf/captain-hook/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/capt-hook)](https://pypi.org/project/capt-hook/)
+[![License: PolyForm Noncommercial](https://img.shields.io/badge/license-PolyForm--Noncommercial--1.0.0-blue)](https://github.com/yasyf/captain-hook/blob/main/LICENSE)
+
+## Get started
+
+```bash
+uvx capt-hook init
+```
+
+`init` scaffolds `.claude/hooks/`, wires Claude Code's settings, and arms the session reviewer. One `block_command` later, a force-push dies at `PreToolUse` and the hook's inline tests run green:
+
+<img src="https://github.com/yasyf/captain-hook/raw/main/docs/assets/demo.png" alt="Terminal running 'uvx capt-hook test' — a hook blocks git push --force and both inline tests pass" width="700">
+
+Driving with an agent? Paste this:
+
+```text
+/plugin marketplace add yasyf/captain-hook
+/plugin install captain-hook@captain-hook
+```
+
+<details>
+<summary>Prefer a prompt over the plugin?</summary>
+
+```text
+Run `uvx capt-hook init` in this repo, write one hook that blocks force-pushes,
+and verify it with `uvx capt-hook test`. Read https://yasyf.github.io/captain-hook/
+if you get stuck.
+```
+
+</details>
+
+---
+
+## Use cases
+
+### Block force-push and rm -rf before they run
+
+One bad Bash call rewrites shared history or eats a directory, and by the time you spot it in the transcript it already ran. Declare the block once, tests inline:
+
+```python
+# .claude/hooks/safety.py
+from captain_hook import Allow, Block, Input, block_command
+
+block_command(
+    ["git", "push", "--force"],
+    reason="Force-pushing rewrites shared history",
+    hint="Use `git push --force-with-lease` instead",
+    tests={
+        Input(command="git push --force"): Block(),
+        Input(command="git push origin main"): Allow(),
+    },
+)
+```
+
+The next `git push --force` never executes: the agent sees `BLOCKED: Force-pushing rewrites shared history` plus the hint, and reaches for `--force-with-lease` instead. `rm -rf` is one more `block_command` away.
+
+### Turn repeated corrections into rules Claude can't forget
+
+You've typed "use uv, not pip" in a dozen sessions, and session thirteen makes the same mistake. After `init`, the session reviewer reads each transcript as the session ends, keeps the corrections that are standing rules, and — once a pattern proves itself across sessions — opens a PR that codifies it as a hook. Watch the pipeline:
+
+```bash
+uvx capt-hook status
+```
+
+The dashboard lists every correction it's tracking, staged from first sighting to open PR. You review the PR like any other; merged hooks enforce the rule from then on.
+
+### Gate "done" until the tests actually pass
+
+The agent declares victory while the suite is red. A Stop gate holds the line:
+
+```python
+# .claude/hooks/quality.py
+from captain_hook import RanCommand, TouchedFile, gate
+
+gate(
+    "You edited Python files but never ran the tests. Run `uv run pytest` before finishing.",
+    only_if=[TouchedFile("**/*.py")],
+    skip_if=[RanCommand(r"\bpytest\b")],
+)
+```
+
+The agent can't end the turn until a pytest run shows up in the transcript, and the gate stands down on its own once one does.
+
+## More in the docs
+
+- **Session reviewer** — the full corrections lifecycle, from transcript to merged hook PR — [guide](https://yasyf.github.io/captain-hook/docs/guide/session-reviewer.html)
+- **Conditions** — typed filters over tools, files, commands, and transcript history — [guide](https://yasyf.github.io/captain-hook/docs/guide/conditions.html)
+- **LLM hooks** — gate on a model's verdict when a regex can't decide — [guide](https://yasyf.github.io/captain-hook/docs/guide/llm-hooks.html)
+- **Workflows** — multi-step Stop gates with artifact checks and checklists — [guide](https://yasyf.github.io/captain-hook/docs/guide/workflows.html)
+- **Packs** — the shipped `general`, `python`, and `go` hook packs — [guide](https://yasyf.github.io/captain-hook/docs/guide/packs.html)
+- **Testing** — run `uvx capt-hook test --json` in CI so a regressed hook fails the build — [guide](https://yasyf.github.io/captain-hook/docs/guide/testing.html)
+
+Read the [docs](https://yasyf.github.io/captain-hook/) for the full guide. Licensed under [PolyForm Noncommercial 1.0.0](https://github.com/yasyf/captain-hook/blob/main/LICENSE), free for noncommercial use.

capt_hook-6.5.0/captain_hook/packs/general/capt-hook.toml

@@ -0,0 +1,5 @@
+name = "general"
+version = "0.10.0"
+description = "Language-agnostic guards: git/command safety, doc & prompt nudges, task & plan discipline, code-review + docs-freshness gates, and a detour check-in nudge."
+hooks = "."
+nlp = true

capt_hook-6.5.0/captain_hook/packs/general/detours.py

@@ -0,0 +1,151 @@
+from __future__ import annotations
+
+from captain_hook import (
+    Allow,
+    Event,
+    Input,
+    Signal,
+    Signals,
+    Tool,
+    Warn,
+    llm_nudge,
+)
+
+llm_nudge(
+    """You are a senior engineer watching another engineer ("the agent") mid-task. You are
+running in agent mode in the project's working directory, with read tools. Your one job:
+decide whether the agent has veered onto an UNREQUESTED DETOUR — side work nobody asked
+for — without checking in first.
+
+Read first, judge second:
+- The session transcript is rendered above inside `<transcript path="...">`; long content is
+  clipped (you'll see `…(+Nch)` markers). From the full history (prefer `cc-transcript
+  show`/`grep`; else read the file) establish: (1) what was actually ASKED — the user's
+  original request plus any later redirections or standing permissions — and (2) what the
+  agent is doing RIGHT NOW — the just-run tool call and the last few assistant messages.
+
+Discriminator: the current work is either (a) the requested task, (b) a necessary
+prerequisite of it (the task cannot land or be verified without it), or (c) authorized —
+the user said some form of "also…", "while you're there…", "fix anything you find", or it
+is a small stewardship fix inside code the task already touches. Any of those -> fire=false.
+Otherwise — the agent noticed something adjacent and started acting on it without surfacing
+it — fire=true.
+
+Detour tells (lean fire=true): "while I'm here" / "might as well" / "let me also" followed
+by edits to files the task doesn't need; fixing or refactoring code the request never
+mentioned and the task doesn't depend on; a cleanup sweep starting mid-task; chasing a side
+mystery at length while the requested work sits unfinished.
+
+Do NOT fire when: the side work blocks the task (a broken build or failing test the change
+trips over); it's a small stewardship fix in a file already being edited for the task; the
+user pre-authorized it; the agent is gathering context it needs; or the agent already
+surfaced the discovery and offered options instead of acting.
+
+<examples>
+<example fire="true">
+Asked: "rename the config flag". Agent: "While I'm here, the retry logic in client.py looks
+wrong — let me fix that too", then edits client.py.
+Unrequested fix in a file the rename never touches.
+</example>
+<example fire="true">
+Asked: "add a --json flag". Agent: "I also noticed the error handling is inconsistent
+across commands; I'll clean that up as well", then starts a multi-file sweep.
+Scope expansion nobody asked for, no options offered.
+</example>
+<example fire="false">
+Asked: "fix the failing test". Agent: "The fixture helper it calls has the actual bug —
+fixing that first."
+A prerequisite: the requested fix cannot land without it.
+</example>
+<example fire="false">
+User said "clean up anything you find along the way"; agent fixes a stale docstring in a
+file it was already editing.
+Pre-authorized stewardship.
+</example>
+<example fire="false">
+Agent: "I noticed X while working on Y — options: (1) finish Y and file X as a follow-up,
+(2) fix X now, (3) ignore it. Which?"
+Already surfacing options instead of acting.
+</example>
+</examples>
+
+When uncertain, return fire=false. A missed detour costs one review comment; a false alarm
+on legitimate work teaches the agent to ignore this nudge. Fire only when the current action
+is clearly outside both the request and its prerequisites. Put your reasoning (under 50
+words, naming the detour and the requested task) in `reasoning`.""",
+    message=lambda r: (
+        f"This looks like a detour — side work nobody asked for. {r.reasoning} "
+        "Stop and check in before acting: say what you noticed, then propose 2-4 concrete "
+        "options (finish the task and file this as a follow-up; pause and fix it now; ignore "
+        "it) and let the user pick — or, if you are a delegated agent, stop and return early "
+        "with findings plus options for your orchestrator instead of improvising. "
+        "See: AGENTS.md § Ask Before Assuming."
+    ),
+    only_if=[Tool("Edit|Write|MultiEdit|NotebookEdit|Bash")],
+    events=Event.PostToolUse,
+    signals=Signals(
+        [
+            Signal(pattern=r"(?i)\bwhile (?:I'm|I am|we're|we are) (?:here|at it|in (?:here|there))\b", weight=2),
+            Signal(pattern=r"(?i)\bmight as well\b", weight=2),
+            Signal(pattern=r"(?i)\b(?:let me|I'll|I will) also\b", weight=2),
+            Signal(pattern=r"(?i)\bas a bonus\b", weight=2),
+            Signal(pattern=r"(?i)\bI (?:also )?noticed\b", weight=1),
+            Signal(pattern=r"(?i)\b(?:unrelated|a side note|tangent)\b", weight=1),
+            Signal(pattern=r"(?i)\bone more thing\b", weight=1),
+            Signal(pattern=r"(?i)\bquick(?:ly)? (?:fix|clean|tidy|refactor)\w*\b", weight=1),
+        ],
+        threshold=2,
+        window=8,
+    ),
+    tests={
+        Input(
+            file="client.py",
+            content="retry = 3\n",
+            transcript=[
+                {
+                    "type": "assistant",
+                    "message": {
+                        "content": [
+                            {"type": "text", "text": "While I'm here, the retry logic looks wrong — fixing it too."}
+                        ]
+                    },
+                }
+            ],
+        ): Warn(pattern="detour"),
+        Input(
+            command="./scripts/cleanup.sh",
+            transcript=[
+                {
+                    "type": "assistant",
+                    "message": {
+                        "content": [
+                            {"type": "text", "text": "I also noticed stale artifacts. One more thing to clean up."}
+                        ]
+                    },
+                }
+            ],
+        ): Warn(pattern="options"),
+        Input(
+            file="flags.py",
+            content="json_flag = True\n",
+            transcript=[
+                {
+                    "type": "assistant",
+                    "message": {"content": [{"type": "text", "text": "Implementing the requested --json flag now."}]},
+                }
+            ],
+        ): Allow(),
+        Input(
+            tool="Read",
+            file="client.py",
+            transcript=[
+                {
+                    "type": "assistant",
+                    "message": {
+                        "content": [{"type": "text", "text": "While I'm here, might as well look at the retry logic."}]
+                    },
+                }
+            ],
+        ): Allow(),
+    },
+)

{capt_hook-6.4.0 → capt_hook-6.5.0}/pyproject.toml

@@ -1,8 +1,8 @@
 [project]
 name = "capt-hook"
 # Inert sentinel — the real version is stamped from the release tag (uv version --frozen).
-version = "6.4.0"
-description = "Declarative hook framework for Claude Code"
+version = "6.5.0"
+description = "Stop repeating yourself to Claude."
 readme = "README.md"
 license = "PolyForm-Noncommercial-1.0.0"
 license-files = ["LICENSE"]

capt_hook-6.4.0/PKG-INFO

@@ -1,137 +0,0 @@
-Metadata-Version: 2.4
-Name: capt-hook
-Version: 6.4.0
-Summary: Declarative hook framework for Claude Code
-Keywords: claude,claude-code,hooks,llm,agents,guardrails,cli
-Author: Yasyf Mohamedali
-Author-email: Yasyf Mohamedali <yasyfm@gmail.com>
-License-Expression: PolyForm-Noncommercial-1.0.0
-License-File: LICENSE
-Classifier: Development Status :: 4 - Beta
-Classifier: Intended Audience :: Developers
-Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Topic :: Software Development :: Quality Assurance
-Classifier: Topic :: Software Development :: Testing
-Classifier: Typing :: Typed
-Requires-Dist: cc-transcript>=7.1,<8
-Requires-Dist: pydantic>=2.0
-Requires-Dist: pydantic-settings>=2.0
-Requires-Dist: tree-sitter>=0.24
-Requires-Dist: tree-sitter-bash>=0.23
-Requires-Dist: ast-grep-py>=0.39,<1
-Requires-Dist: funcy>=2.0
-Requires-Dist: spacy>=3.7
-Requires-Dist: click>=8
-Requires-Dist: rich>=13
-Requires-Dist: orjsonl>=1.0
-Requires-Dist: wn>=1.1.0
-Requires-Dist: lazy-object-proxy>=1.12.0
-Requires-Dist: filelock>=3
-Requires-Dist: loguru>=0.7.3
-Requires-Dist: spawnllm>=0.5.2,<0.6
-Requires-Dist: pytest>=8.0 ; extra == 'dev'
-Requires-Dist: pytest-asyncio>=0.24 ; extra == 'dev'
-Requires-Dist: pyright>=1.1 ; extra == 'dev'
-Requires-Dist: pyyaml>=6 ; extra == 'dev'
-Requires-Dist: ruff>=0.8 ; extra == 'dev'
-Requires-Python: >=3.13
-Project-URL: Homepage, https://github.com/yasyf/captain-hook
-Project-URL: Documentation, https://yasyf.github.io/captain-hook/
-Project-URL: Repository, https://github.com/yasyf/captain-hook
-Project-URL: Issues, https://github.com/yasyf/captain-hook/issues
-Project-URL: Changelog, https://github.com/yasyf/captain-hook/blob/main/CHANGELOG.md
-Provides-Extra: dev
-Description-Content-Type: text/markdown
-
-# captain-hook
-
-![captain-hook banner](https://github.com/yasyf/captain-hook/raw/main/docs/assets/readme-banner.webp)
-
-[![PyPI](https://img.shields.io/pypi/v/capt-hook.svg)](https://pypi.org/project/capt-hook/)
-[![Python](https://img.shields.io/pypi/pyversions/capt-hook.svg)](https://pypi.org/project/capt-hook/)
-[![Docs](https://github.com/yasyf/captain-hook/actions/workflows/docs.yml/badge.svg)](https://yasyf.github.io/captain-hook/)
-[![License: PolyForm-Noncommercial-1.0.0](https://img.shields.io/badge/License-PolyForm--Noncommercial--1.0.0-blue.svg)](https://github.com/yasyf/captain-hook/blob/main/LICENSE)
-
-Guardrails for Claude Code, written as typed, testable data — and learned from the corrections you give Claude.
-
-A captain-hook hook is declarative Python: an event, some conditions, an action. Block a footgun before it runs, nudge the agent off a bad pattern, gate "done" until the tests pass. Then captain-hook closes the loop: it reads the corrections you give Claude as you work and opens pull requests that codify the durable ones as new hooks. You write the first few; it writes the rest.
-
-## Install
-
-captain-hook needs no install — it runs through [uvx](https://docs.astral.sh/uv/). From your project root:
-
-```bash
-uvx capt-hook init
-```
-
-`init` scaffolds `.claude/hooks/`, wires Claude Code's settings, registers the captain-hook plugin so its skills install on workspace-trust, and arms the [session reviewer](#it-learns-from-your-corrections). Or do it all from a session. Run `/plugin marketplace add yasyf/captain-hook`, then ask Claude to "set up captain hook".
-
-## Your first hook
-
-A hook is an event, some conditions, and an action. This one stops the agent from finishing a UI change it never looked at:
-
-```python
-# .claude/hooks/visual_review.py
-from captain_hook import gate, TouchedFile, UsedSkill
-
-gate(
-    "You edited UI files. Open them with agent-browser and verify they render before finishing.",
-    only_if=[TouchedFile("**/src/routes/**", "**/src/components/**")],
-    skip_if=[UsedSkill("agent-browser")],
-)
-```
-
-`only_if` arms the gate only when UI files changed; `skip_if` stands it down once the agent has done the review. Conditions match tools, files, commands, and even which skills the agent used.
-
-## It learns from your corrections
-
-Most hooks you'll never write by hand.
-
-The corrections you give Claude as you work are exactly the rules a hook should enforce: "never force-push", "use `uv`, not `pip`", "you weakened that test". Writing the hook by hand is friction you skip in the moment, so the **session reviewer** notices for you. When a session ends, it reads the transcript, finds the durable corrections and the hooks that misfired, judges which ones are standing rules and which are one-offs, and once a pattern proves itself across sessions, opens a pull request that adds the hook — or fixes the one that misfired. You review the PR like any other.
-
-It's on by default after `init`. Turn it off for a repo with `uvx capt-hook review disable`. The [session reviewer guide](https://yasyf.github.io/captain-hook/docs/guide/session-reviewer.html) covers the prerequisites (an authenticated `claude` and `gh`) and the `HOOKS_REVIEW_*` thresholds.
-
-## Tested like code
-
-Every deterministic hook carries inline tests, so a broken hook fails like broken code:
-
-```python
-# .claude/hooks/safety.py
-from captain_hook import Allow, Block, Input, block_command
-
-block_command(
-    ["git", "stash"],
-    reason="Use the team's VCS workflow for shelving changes",
-    hint="Commit a WIP change instead of stashing",
-    tests={
-        Input(command="git stash"): Block(),
-        Input(command="git status"): Allow(),
-    },
-)
-```
-
-Run them from your project root, where `--hooks` defaults to `.claude/hooks`:
-
-```bash
-uvx capt-hook test
-```
-
-Wire that into CI and you catch a broken hook the way you catch broken code.
-
-## What it's for
-
-- Block footguns before they run on `PreToolUse`: force-push, `rm -rf`, package-manager traps.
-- Steer the agent with feedback that fires on the patterns it actually emits: repeated failures, weakened tests, missed conventions.
-- Hold the line on multi-step work with Stop gates and artifact checks, so the agent can't call it "done" before the tests run or the report's written.
-- Keep all of it testable; every hook ships with inline tests that run in CI.
-
-## Docs
-
-[Read the docs](https://yasyf.github.io/captain-hook/) for the full guide to conditions, primitives, LLM hooks, workflows, state, and real-world patterns. To work on captain-hook itself, see the [development guide](https://yasyf.github.io/captain-hook/docs/development/).
-
-## License
-
-Licensed under [PolyForm Noncommercial 1.0.0](LICENSE), free for noncommercial use.

capt_hook-6.4.0/README.md

@@ -1,89 +0,0 @@
-# captain-hook
-
-![captain-hook banner](https://github.com/yasyf/captain-hook/raw/main/docs/assets/readme-banner.webp)
-
-[![PyPI](https://img.shields.io/pypi/v/capt-hook.svg)](https://pypi.org/project/capt-hook/)
-[![Python](https://img.shields.io/pypi/pyversions/capt-hook.svg)](https://pypi.org/project/capt-hook/)
-[![Docs](https://github.com/yasyf/captain-hook/actions/workflows/docs.yml/badge.svg)](https://yasyf.github.io/captain-hook/)
-[![License: PolyForm-Noncommercial-1.0.0](https://img.shields.io/badge/License-PolyForm--Noncommercial--1.0.0-blue.svg)](https://github.com/yasyf/captain-hook/blob/main/LICENSE)
-
-Guardrails for Claude Code, written as typed, testable data — and learned from the corrections you give Claude.
-
-A captain-hook hook is declarative Python: an event, some conditions, an action. Block a footgun before it runs, nudge the agent off a bad pattern, gate "done" until the tests pass. Then captain-hook closes the loop: it reads the corrections you give Claude as you work and opens pull requests that codify the durable ones as new hooks. You write the first few; it writes the rest.
-
-## Install
-
-captain-hook needs no install — it runs through [uvx](https://docs.astral.sh/uv/). From your project root:
-
-```bash
-uvx capt-hook init
-```
-
-`init` scaffolds `.claude/hooks/`, wires Claude Code's settings, registers the captain-hook plugin so its skills install on workspace-trust, and arms the [session reviewer](#it-learns-from-your-corrections). Or do it all from a session. Run `/plugin marketplace add yasyf/captain-hook`, then ask Claude to "set up captain hook".
-
-## Your first hook
-
-A hook is an event, some conditions, and an action. This one stops the agent from finishing a UI change it never looked at:
-
-```python
-# .claude/hooks/visual_review.py
-from captain_hook import gate, TouchedFile, UsedSkill
-
-gate(
-    "You edited UI files. Open them with agent-browser and verify they render before finishing.",
-    only_if=[TouchedFile("**/src/routes/**", "**/src/components/**")],
-    skip_if=[UsedSkill("agent-browser")],
-)
-```
-
-`only_if` arms the gate only when UI files changed; `skip_if` stands it down once the agent has done the review. Conditions match tools, files, commands, and even which skills the agent used.
-
-## It learns from your corrections
-
-Most hooks you'll never write by hand.
-
-The corrections you give Claude as you work are exactly the rules a hook should enforce: "never force-push", "use `uv`, not `pip`", "you weakened that test". Writing the hook by hand is friction you skip in the moment, so the **session reviewer** notices for you. When a session ends, it reads the transcript, finds the durable corrections and the hooks that misfired, judges which ones are standing rules and which are one-offs, and once a pattern proves itself across sessions, opens a pull request that adds the hook — or fixes the one that misfired. You review the PR like any other.
-
-It's on by default after `init`. Turn it off for a repo with `uvx capt-hook review disable`. The [session reviewer guide](https://yasyf.github.io/captain-hook/docs/guide/session-reviewer.html) covers the prerequisites (an authenticated `claude` and `gh`) and the `HOOKS_REVIEW_*` thresholds.
-
-## Tested like code
-
-Every deterministic hook carries inline tests, so a broken hook fails like broken code:
-
-```python
-# .claude/hooks/safety.py
-from captain_hook import Allow, Block, Input, block_command
-
-block_command(
-    ["git", "stash"],
-    reason="Use the team's VCS workflow for shelving changes",
-    hint="Commit a WIP change instead of stashing",
-    tests={
-        Input(command="git stash"): Block(),
-        Input(command="git status"): Allow(),
-    },
-)
-```
-
-Run them from your project root, where `--hooks` defaults to `.claude/hooks`:
-
-```bash
-uvx capt-hook test
-```
-
-Wire that into CI and you catch a broken hook the way you catch broken code.
-
-## What it's for
-
-- Block footguns before they run on `PreToolUse`: force-push, `rm -rf`, package-manager traps.
-- Steer the agent with feedback that fires on the patterns it actually emits: repeated failures, weakened tests, missed conventions.
-- Hold the line on multi-step work with Stop gates and artifact checks, so the agent can't call it "done" before the tests run or the report's written.
-- Keep all of it testable; every hook ships with inline tests that run in CI.
-
-## Docs
-
-[Read the docs](https://yasyf.github.io/captain-hook/) for the full guide to conditions, primitives, LLM hooks, workflows, state, and real-world patterns. To work on captain-hook itself, see the [development guide](https://yasyf.github.io/captain-hook/docs/development/).
-
-## License
-
-Licensed under [PolyForm Noncommercial 1.0.0](LICENSE), free for noncommercial use.

capt_hook-6.4.0/captain_hook/packs/general/capt-hook.toml

@@ -1,5 +0,0 @@
-name = "general"
-version = "0.9.0"
-description = "Language-agnostic guards: git/command safety, doc & prompt nudges, task & plan discipline, and code-review + docs-freshness gates."
-hooks = "."
-nlp = true