claude-dev-env 1.38.1 → 1.40.0

package/_shared/pr-loop/scripts/tests/test_post_audit_thread_constants.py

@@ -0,0 +1,127 @@
+"""Tests for post_audit_thread_constants.py extracted constant set."""
+
+import importlib.util
+from pathlib import Path
+from types import ModuleType
+
+
+def _load_constants_module() -> ModuleType:
+    module_path = (
+        Path(__file__).parent.parent / "config" / "post_audit_thread_constants.py"
+    )
+    specification = importlib.util.spec_from_file_location(
+        "config.post_audit_thread_constants", module_path
+    )
+    assert specification is not None
+    assert specification.loader is not None
+    module = importlib.util.module_from_spec(specification)
+    specification.loader.exec_module(module)
+    return module
+
+
+constants_module = _load_constants_module()
+
+
+def test_http_request_content_type_is_application_json() -> None:
+    assert constants_module.HTTP_REQUEST_CONTENT_TYPE == "application/json"
+
+
+def test_http_method_post_constant_is_post() -> None:
+    assert constants_module.HTTP_METHOD_POST == "POST"
+
+
+def test_http_header_authorization_constant_is_authorization() -> None:
+    assert constants_module.HTTP_HEADER_AUTHORIZATION == "Authorization"
+
+
+def test_http_header_accept_constant_is_accept() -> None:
+    assert constants_module.HTTP_HEADER_ACCEPT == "Accept"
+
+
+def test_http_header_content_type_constant_is_content_type() -> None:
+    assert constants_module.HTTP_HEADER_CONTENT_TYPE == "Content-Type"
+
+
+def test_http_header_github_api_version_constant_is_x_github_api_version() -> None:
+    assert constants_module.HTTP_HEADER_GITHUB_API_VERSION == "X-GitHub-Api-Version"
+
+
+def test_http_header_user_agent_constant_is_user_agent() -> None:
+    assert constants_module.HTTP_HEADER_USER_AGENT == "User-Agent"
+
+
+def test_http_authorization_bearer_prefix_is_bearer_with_trailing_space() -> None:
+    prefix = constants_module.HTTP_AUTHORIZATION_BEARER_PREFIX
+    assert prefix == "Bearer "
+    assert prefix.endswith(" ")
+
+
+def test_http_request_timeout_seconds_is_positive_int() -> None:
+    timeout_seconds = constants_module.HTTP_REQUEST_TIMEOUT_SECONDS
+    assert isinstance(timeout_seconds, int)
+    assert timeout_seconds > 0
+
+
+def test_error_response_preview_chars_is_positive_int() -> None:
+    preview_chars = constants_module.ERROR_RESPONSE_PREVIEW_CHARS
+    assert isinstance(preview_chars, int)
+    assert preview_chars > 0
+
+
+def test_single_review_api_path_template_uses_pr_number_placeholder() -> None:
+    template_text = constants_module.SINGLE_REVIEW_API_PATH_TEMPLATE
+    assert "{owner}" in template_text
+    assert "{repo}" in template_text
+    assert "{pr_number}" in template_text
+    assert "{review_id}" in template_text
+
+
+def test_single_review_comments_api_path_template_uses_pr_number_placeholder() -> None:
+    template_text = constants_module.SINGLE_REVIEW_COMMENTS_API_PATH_TEMPLATE
+    assert "{owner}" in template_text
+    assert "{repo}" in template_text
+    assert "{pr_number}" in template_text
+    assert "{review_id}" in template_text
+    assert template_text.endswith("/comments")
+
+
+def test_audit_body_skeleton_marker_tokens_present() -> None:
+    open_marker = constants_module.AUDIT_BODY_SKELETON_OPEN_MARKER
+    close_marker = constants_module.AUDIT_BODY_SKELETON_CLOSE_MARKER
+    assert open_marker.startswith("<!--") and open_marker.endswith("-->")
+    assert close_marker.startswith("<!--") and close_marker.endswith("-->")
+    assert open_marker != close_marker
+
+
+def test_template_path_resolves_to_existing_markdown_file() -> None:
+    resolved_path = constants_module.template_path()
+    assert resolved_path.is_file(), f"missing: {resolved_path}"
+    assert resolved_path.suffix == ".md"
+
+
+def test_template_contains_skeleton_markers() -> None:
+    resolved_path = constants_module.template_path()
+    template_text = resolved_path.read_text(encoding="utf-8")
+    assert constants_module.AUDIT_BODY_SKELETON_OPEN_MARKER in template_text
+    assert constants_module.AUDIT_BODY_SKELETON_CLOSE_MARKER in template_text
+
+
+def test_live_test_fixture_names_are_not_exposed_from_production_config_module() -> None:
+    forbidden_attribute_names = [
+        "LIVE_TEST_OWNER",
+        "LIVE_TEST_REPO",
+        "LIVE_TEST_BRANCH_PREFIX",
+        "LIVE_TEST_PR_TITLE",
+        "LIVE_TEST_PR_BODY",
+        "LIVE_TEST_BASE_BRANCH",
+        "LIVE_TEST_FIXTURE_FILENAME",
+        "LIVE_TEST_FIXTURE_CONTENT",
+        "LIVE_TEST_FIXTURE_LINE_FOR_FINDING_ONE",
+        "LIVE_TEST_FIXTURE_LINE_FOR_FINDING_TWO",
+        "LIVE_TEST_FIXTURE_LINE_FOR_FINDING_THREE",
+    ]
+    for each_attribute_name in forbidden_attribute_names:
+        assert not hasattr(constants_module, each_attribute_name), (
+            f"production config module exposes test-only fixture "
+            f"{each_attribute_name!r}; move it to test_post_audit_thread.py"
+        )

package/_shared/pr-loop/scripts/tests/test_preflight.py

@@ -690,3 +690,44 @@ def test_main_prints_no_related_tests_when_get_changed_files_returns_empty(
     assert exit_code == 0
     captured = capsys.readouterr()
     assert "no related tests found" in captured.err
+
+
+def test_main_should_halt_when_env_var_lists_bugteam(
+    monkeypatch: pytest.MonkeyPatch,
+    capsys: pytest.CaptureFixture[str],
+) -> None:
+    """CLAUDE_REVIEWS_DISABLED=bugteam must halt preflight with the dedicated exit code."""
+    monkeypatch.setenv("CLAUDE_REVIEWS_DISABLED", "bugteam")
+    monkeypatch.delenv("BUGTEAM_PREFLIGHT_SKIP", raising=False)
+    exit_code = preflight.main(["--no-pytest"])
+    assert exit_code == preflight.EXIT_CODE_BUGTEAM_DISABLED_VIA_ENV
+    captured = capsys.readouterr()
+    assert "CLAUDE_REVIEWS_DISABLED" in captured.err
+    assert "bugteam" in captured.err
+
+
+def test_main_should_continue_when_env_var_omits_bugteam(
+    monkeypatch: pytest.MonkeyPatch,
+    tmp_path: Path,
+) -> None:
+    """CLAUDE_REVIEWS_DISABLED without the bugteam token must not halt preflight."""
+    monkeypatch.setenv("CLAUDE_REVIEWS_DISABLED", "copilot,bugbot")
+    monkeypatch.delenv("BUGTEAM_PREFLIGHT_SKIP", raising=False)
+    claude_hooks_path = tmp_path / ".claude" / "hooks" / "git-hooks"
+    claude_hooks_path.mkdir(parents=True)
+    with patch("subprocess.run") as mock_run:
+        mock_run.return_value = _make_completed_process(
+            str(claude_hooks_path) + "\n", returncode=0
+        )
+        exit_code = preflight.main(["--no-pytest"])
+    assert exit_code != preflight.EXIT_CODE_BUGTEAM_DISABLED_VIA_ENV
+
+
+def test_main_should_halt_when_env_var_contains_uppercase_or_whitespace_bugteam_token(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    """Token matching must be case-insensitive and whitespace-tolerant."""
+    monkeypatch.setenv("CLAUDE_REVIEWS_DISABLED", " BugTeam , copilot ")
+    monkeypatch.delenv("BUGTEAM_PREFLIGHT_SKIP", raising=False)
+    exit_code = preflight.main(["--no-pytest"])
+    assert exit_code == preflight.EXIT_CODE_BUGTEAM_DISABLED_VIA_ENV

package/_shared/pr-loop/scripts/tests/test_reviews_disabled.py

@@ -0,0 +1,36 @@
+"""Direct unit tests for the shared reviews_disabled helper."""
+
+import importlib.util
+from pathlib import Path
+from types import ModuleType
+
+import pytest
+
+
+def _load_reviews_disabled_module() -> ModuleType:
+    module_path = Path(__file__).parent.parent / "reviews_disabled.py"
+    specification = importlib.util.spec_from_file_location(
+        "reviews_disabled", module_path
+    )
+    assert specification is not None
+    assert specification.loader is not None
+    module = importlib.util.module_from_spec(specification)
+    specification.loader.exec_module(module)
+    return module
+
+
+reviews_disabled = _load_reviews_disabled_module()
+
+
+def test_is_bugteam_disabled_via_env_returns_true_when_env_lists_bugteam(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    monkeypatch.setenv("CLAUDE_REVIEWS_DISABLED", "bugteam")
+    assert reviews_disabled.is_bugteam_disabled_via_env() is True
+
+
+def test_is_bugteam_disabled_via_env_returns_false_when_env_is_empty(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    monkeypatch.delenv("CLAUDE_REVIEWS_DISABLED", raising=False)
+    assert reviews_disabled.is_bugteam_disabled_via_env() is False

package/_shared/pr-loop/state-schema.md

@@ -11,7 +11,7 @@ State each PR-loop workflow tracks across iterations. Workflows differ on persis
 | `last_findings` | object | `{p0, p1, p2, total}` count of findings from most recent AUDIT |
 | `audit_log` | list[str] | Per-iteration one-line summaries for the final report |
 | `starting_sha` | str | `git rev-parse HEAD` at workflow start |
-| `loop_comment_index` | dict | `{finding_id: {finding_comment_id, finding_comment_url, used_fallback, fix_status, ...}}` |
+| `loop_comment_index` | dict | `{finding_id: {finding_comment_id, finding_comment_url, thread_node_id, fix_status, ...}}` (`thread_node_id` is the PR review thread node id — `PRRT_kwDOxxx` — captured at audit time when calling `get_review_comments`, used by `resolve_thread` at FIX time) |
 
 ## Workflow-specific extensions
 

package/agents/clean-coder.md

@@ -8,7 +8,7 @@ color: green
 
 # Clean Coder — Zero-Defect Code Generation
 
-You are the definitive code-writing agent. You produce code so clean that reviewers find nothing. Every rule from CODE_RULES.md and every dimension from the readability rubric is internalized into your generation process. The goal: `/check` and `/readability-review` return CLEAN on every file you touch.
+You are the definitive code-writing agent. You produce code so clean that reviewers find nothing. Every rule from CODE_RULES.md and every dimension from the readability rubric is internalized into your generation process. The goal: `/check` returns CLEAN on every file you touch.
 
 **Announce at start:** "Using clean-coder agent — CODE_RULES.md internalized, targeting 160/160 readability."
 
@@ -445,7 +445,7 @@ Code clean-coder writes will be audited later against the A–K bug categories f
 Every line you write or modify will:
 - Score 160/160 on the 8-dimension readability rubric
 - Satisfy every hook-enforced gate so each write succeeds on the first attempt
-- Return CLEAN from `/check`, `/review-code`, and `/readability-review`
+- Return CLEAN from `/check` and `/review-code`
 - Use complete type hints on every parameter and return
 - Pass `mypy_validator.py` cleanly — every file is mypy-clean at write time
 - Land in the format the project's `auto_formatter.py` produces — the formatter runs at write time, but generation should already match the canonical Black/Prettier output

package/agents/pr-description-writer.md

@@ -1,87 +1,185 @@
 ---
 name: pr-description-writer
-description: "MANDATORY agent for writing PR descriptions, commit messages, and PR comments. Enforced by global hook — all gh pr create/edit and git commit commands are blocked until this agent generates the description. Produces plain-language, file-grouped descriptions explaining WHY changes were made."
+description: "MANDATORY agent for writing PR descriptions, commit messages, PR comments, and issue comments. Enforced by the pr_description_enforcer PreToolUse hook -- every gh pr create/edit invocation that carries a body is blocked until this agent has authored it. Produces output in the style of merged pull requests in anthropics/claude-code, anthropics/claude-code-action, and anthropics/claude-cli-internal: trivial one-liners for mechanical changes, intro-paragraph + Changes + Test plan for standard fixes, full Problem/Fix/Verification with optional Caveat/Runtime-behavior for heavy changes. Triggers: write a PR body, draft a PR description, author the commit message, comment on the PR, comment on the issue, prepare the body for gh pr create / gh pr edit / gh pr comment / gh issue comment, generate the body-file, fix the blocked PR description."
 tools: Read,Grep,Glob,Bash
 model: haiku
 ---
 
 # PR Description Writer
 
-You write PR descriptions, commit messages, and PR/issue comments. You do ONE thing: produce clear, structured, plain-language descriptions that explain WHY changes were made.
+You author PR descriptions, commit messages, and PR/issue comments in the shape that merged pull requests in `anthropics/claude-code`, `anthropics/claude-code-action`, and `anthropics/claude-cli-internal` take. You pick the shape from the diff. You write the body text and nothing else -- the caller passes it to `gh pr create --body-file`.
 
-## Style Rules
+## TOC
 
-### 1. Group production code changes BY FILE with plain-language WHY
+- Process (the 4-step checklist)
+- Sizing (Trivial / Standard / Heavy)
+- Shape 1: Trivial (sectionless one-liner)
+- Shape 2: Standard (intro + Changes + Test plan)
+- Shape 3: Heavy (intro + Problem + Fix + Verification + optional)
+- File reference style
+- Cross-references
+- Markers and footers
+- Commit messages
+- Gotchas
+- Refusals
 
-For each production file changed, write a short paragraph:
-- **Bold the filename** (no path, just the file)
-- Explain the problem in layman terms (what went wrong / what was missing)
-- Explain the fix in layman terms (what the change does)
-- No jargon. No code snippets. No technical implementation details.
+The companion guide (`packages/claude-dev-env/docs/PR_DESCRIPTION_GUIDE.md`) carries the section-vocabulary table and the hook's pass/block contract -- do not duplicate that content here.
 
-Example:
-> **pullEngine.ts** — Added a timestamp check to prevent background data pulls from overwriting recent local changes. Before this fix, the pull engine would blindly overwrite any record marked as 'synced', even if it had just been updated locally moments ago.
-
-### 2. Group test/config changes as bullet points
+## Process
 
-Test file changes, CI config, and tooling changes get summarized as a flat bullet list. No per-file breakdown needed.
+Copy this checklist into your response and check items off as you go:
 
-Example:
-> ### Test fixes (4 files)
-> - Replace fragile timeout calls with deterministic sync waits
-> - Wait for background pull to complete before interacting with data
-> - Disable CSS animations to prevent click instability
+- [ ] Inspect the diff: `git diff <base>...HEAD --stat`, then `git diff <base>...HEAD` for any file whose purpose isn't obvious from the path.
+- [ ] If the branch name or any commit mentions an issue (`fix-1311`, `Fixes #1311`), read it: `gh issue view 1311`.
+- [ ] Pick the shape from the Sizing table.
+- [ ] Write the body in that shape. Output ONLY the body text -- no preamble, no `<body>` tags, no trailing commentary.
 
-### 3. Include verification if applicable
+## Sizing
 
-If tests were run, include actual numbers:
-> ### Verification
-> All 3 test suites pass 50x on CI (3,000 total runs, 0 failures).
+| Signal | Shape |
+|---|---|
+| 1-3 files, mechanical change (pin bump, link fix, typo, single-line config), no behavior change | **Trivial** |
+| Behavior change, bug fix, small feature; under ~15 files | **Standard** |
+| New subsystem, refactor across many files, schema or contract change, anything with a caveat | **Heavy** |
 
-### 4. Commit messages
+Prefer the smaller shape when borderline. Anthropic authors prefer the smaller shape.
 
-For commit messages, use the same principles but compressed:
-- First line: imperative summary (max 72 chars)
-- Body: one paragraph per production file explaining WHY
-- Skip test details unless the commit is test-only
+## Shape 1: Trivial
 
-## Structure Template
+One declarative sentence. No Markdown headers. Optional `Fixes #N` line.
 
 ```
-## Summary
+Pin third-party GitHub Actions references to immutable commit SHAs.
+```
 
-### Production code changes (N files)
+```
+Bump pinned Bun from 1.3.6 to 1.3.14.
 
-**filename.ts** — Plain language explanation of what was wrong and what the fix does.
+Fixes #1311.
+```
 
-**otherfile.tsx** — Plain language explanation.
+## Shape 2: Standard
 
-### Test fixes (N files)
+```
+<One short intro paragraph stating the change and why it matters.
+ Reference the failure mode or user-visible symptom when there is one.>
 
-- Bullet point summaries
-- No per-file breakdown
+Fixes #<n>.
 
-### Verification
+## Changes
 
-Actual test results with numbers.
+- `path/to/file.ext`: short clause describing the change
+- `path/to/other.ext`: short clause
+- `tests/foo.test.ts`: 2 new cases for X
 
 ## Test plan
-- [ ] Checklist items
+
+- `bun test test/foo.test.ts`
+- `bun run typecheck`
+- Manual: reproduce on a branch named `feature/a,b`; confirm no rejection
 ```
 
-## Process
+## Shape 3: Heavy
+
+```
+<Two- to four-sentence intro: scope, motivation, user-visible effect.
+ Link to the prior PR or issue that motivates this one if applicable.>
+
+Fixes #<n>.
+
+## Problem
+
+<Concrete description of the failure mode or gap. Quote the actual
+ error text or a reproduction in a fenced code block when it helps.>
+
+```
+<error or reproduction>
+```
+
+## Fix
+
+<What the change does at the level a reviewer needs to evaluate it.
+ Reference the file or function by path. Don't restate the diff
+ line-by-line.>
+
+- `src/path/file.ts`: brief description
+- `src/path/other.ts`: brief description
+
+## Verification
+
+- Command 1
+- Command 2 (with output count when useful: "666 pass, 0 fail")
+- Manual scenarios walked through
+
+## Caveat
+
+<Anything a reviewer or downstream user needs to know that isn't in
+ the diff. Omit the section when there is no caveat.>
+```
+
+Optional Heavy-shape sections, used only when they earn their place: `## Runtime behavior`, `## Components` (as a path/type/invocation table), `## Backward compatibility`, `## Context`.
+
+## File reference style
+
+- Backtick file paths: `` `src/github/operations/branch.ts` ``.
+- Use the full path from repo root unless the basename is unambiguous within the PR.
+- Per-file change bullets lead with the backticked path and a colon:
+  - `` `src/foo.ts`: whitelists `,` in branch names ``
+- When one file is the centerpiece, bold the backticked filename: `` **`branch.ts`**: ... ``.
+
+## Cross-references
+
+- Same-repo: `#1311`. Cross-repo: `anthropics/claude-code#40576`.
+- `Fixes #N` and `Closes #N` close the issue on merge -- pick one and use it deliberately.
+- `Linear: CC-1723` on its own line.
+- "Follow-up to #<n>" / "Same change as <repo>#<n>" -- short orientation one-liners are welcome.
+
+## Markers and footers
+
+- `<!-- NO CHANGELOG -->` at the end, on its own line, for docs-only or CI-only PRs in repos that auto-generate changelogs from titles.
+- No "Generated with Claude Code" footer. Merged Anthropic PRs do not use one consistently and the commit trailer covers attribution.
+
+## Commit messages
+
+Same shape, compressed:
+
+- First line: imperative summary, max 72 chars. Conventional-commit prefix when the repo uses them (`fix:`, `feat:`, `chore:`, `docs:`, `ci:`, `style:`, `refactor:`).
+- Blank line.
+- Body: one short paragraph stating the Why and the Fix together. Reference the issue when relevant.
+- Skip the body entirely for trivial commits whose first line says everything.
+
+```
+fix: allow , in branch names
+
+git check-ref-format permits commas; the whitelist in
+src/github/operations/branch.ts did not, so PRs whose head
+branch contained a comma failed validation before any git
+operation. Add `,` to the whitelist; same reasoning as
+adding `#` (#1167) and `+` (#1248).
+
+Fixes #1300.
+```
+
+## Gotchas
+
+Highest-signal content. Each item is a real failure mode that has shown up in PR drafts that needed to be rewritten before merge.
+
+- **Don't restate the PR title as the body's first line.** The title is already displayed. Start with the *consequence* the reader cares about.
+- **Don't add `## Why` over a single-paragraph intro.** A header on one paragraph reads as ceremony. The unmarked intro paragraph IS the Why.
+- **Don't add a "Generated with Claude Code" footer.** Anthropic's own merged PRs use this footer inconsistently; defaulting to omit matches the median.
+- **Don't write second-person commentary to the reviewer.** "Please review carefully" / "Let me know if" / "WDYT" don't appear in merged Anthropic PR bodies.
+- **Don't restate the diff in `## Changes`.** Per-file bullets describe the *purpose* of the change in the file, not the line edits. The reviewer reads the diff.
+- **Don't put verification commands in `## Changes`.** They go in `## Test plan` / `## Verification`. Mixing them obscures both.
+- **Don't bold a filename without backticks.** Filenames are code; the canonical form is `` **`branch.ts`**: ... ``, never `**branch.ts**:`.
+- **Don't mix `Fixes #N` and `Closes #N` within one body.** Both close the linked issue on merge -- pick one verb per PR.
+- **Don't add empty section headers.** If `## Caveat` would be empty, drop it. Headers exist to organize content, not to satisfy a template.
+- **Don't hedge.** "should", "might", "I think" -- delete or replace with a verified claim or an explicit "not yet verified" call-out.
+- **Trivial PRs need no sections.** Resist the urge to add `## Summary` over a one-sentence body. The hook does not require headers; the style does not invite them.
+- **The hook permits sectionless bodies.** A single substantive sentence (>= 40 chars of prose after stripping ceremony) passes the `pr_description_enforcer` substantive-prose check. Don't add headers to placate the hook -- the hook isn't asking for them.
 
-1. Read the git diff (staged changes or branch diff against base)
-2. Categorize files: production vs test vs config
-3. For each production file, understand the change and write the WHY
-4. Summarize test/config changes as bullets
-5. Output the description in the template format
+## Refusals
 
-## What NOT to do
+First match wins. Respond with the quoted line exactly and stop:
 
-- No code snippets in descriptions
-- No technical jargon (no "Dexie transaction", say "database transaction")
-- No implementation details (no "added pullStartedAt parameter", say "added a timestamp check")
-- No passive voice ("Fixed X" not "X was fixed")
-- No filler ("This PR..." — just start with the content)
-- No duplicating the diff (the reviewer can read the code)
+- **No diff visible** (e.g., called against an empty branch or before any commits land). Respond: `No diff to describe. Run "git diff <base>...HEAD --stat" first; if the diff is genuinely empty, the PR shouldn't exist.`
+- **Caller asks for prose to be edited into the PR description rather than authored from the diff** (e.g., "add a paragraph saying X to the existing body"). Respond: `Author the body from the diff, not from external prose. Fetch the current diff and re-derive; if the caller has standing instruction text that must appear verbatim, paste it as a Caveat block.`

package/bin/install.mjs

@@ -16,7 +16,7 @@ const PACKAGE_NAME = 'claude-dev-env';
 const PACKAGE_VERSION = JSON.parse(readFileSync(join(PACKAGE_ROOT, 'package.json'), 'utf8')).version;
 const packageRequire = createRequire(import.meta.url);
 
-export const CONTENT_DIRECTORIES = ['rules', 'docs', 'commands', 'agents', 'system-prompts', 'scripts', '_shared'];
+export const CONTENT_DIRECTORIES = ['rules', 'docs', 'commands', 'agents', 'system-prompts', 'scripts', '_shared', 'audit-rubrics'];
 
 export function collectPackageSourceConflicts(packageDirectory) {
     const gitConflictStatusCodes = new Set(['DD', 'AU', 'UD', 'UA', 'DU', 'AA', 'UU']);
@@ -147,17 +147,16 @@ const INSTALL_GROUPS = {
     core: {
         description: 'Development standards, hooks, agents, commands',
         skills: [
-            'anthropic-plan', 'everything-search', 'ingest',
-            'npm-creator', 'pr-review-responder', 'readability-review',
-            'recall', 'remember', 'rule-audit', 'rule-creator',
-            'skill-writer', 'tdd-team'
+            'anthropic-plan', 'everything-search',
+            'pr-review-responder',
+            'recall', 'remember'
         ],
-        includeDirectories: ['rules', 'docs', 'commands', 'agents'],
+        includeDirectories: ['rules', 'docs', 'commands', 'agents', 'audit-rubrics'],
         includeAllHooks: true,
     },
     journal: {
         description: 'Session logging and memory',
-        skills: ['dream', 'session-log', 'session-tidy'],
+        skills: ['session-log', 'session-tidy'],
     },
     research: {
         description: 'Deep research and citation tools',

package/bin/install.test.mjs

@@ -135,6 +135,14 @@ test('CONTENT_DIRECTORIES includes _shared so installer copies _shared/pr-loop/
 });
 
 
+test('CONTENT_DIRECTORIES includes audit-rubrics so installer copies category rubrics and prompts to ~/.claude/audit-rubrics/', () => {
+    assert.ok(
+        CONTENT_DIRECTORIES.includes('audit-rubrics'),
+        'audit-rubrics must be in CONTENT_DIRECTORIES so bugteam can resolve $HOME/.claude/audit-rubrics/{category_rubrics,prompts}/',
+    );
+});
+
+
 test('collectPackageSourceConflicts surfaces both-added and deleted-by-them entries', () => {
     const repositoryRoot = createTemporaryGitRepository();
     try {

package/commands/doc-gist.md

@@ -0,0 +1,16 @@
+---
+description: Upload an HTML file as a secret gist and open the htmlpreview URL. Manual escape hatch when the auto-publish hook's marker route doesn't apply.
+allowed-tools: Bash
+---
+
+Argument: `$ARGUMENTS` is the path to an existing `.html` file.
+
+Run the doc-gist skill's transport script directly:
+
+```
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/doc-gist/scripts/gist_upload.py" --input "$ARGUMENTS"
+```
+
+Quote both URLs (`Gist:` and `Preview:`) from stderr back to the user as clickable markdown links. Surface any `gh gist create failed` error with the suggested `gh auth login` next-step.
+
+When the user asks for a writeup or report rather than handing you a file path, design fresh HTML per [`skills/doc-gist/SKILL.md`](../skills/doc-gist/SKILL.md), include the `<!-- @publish-as-gist -->` marker, and write the file — the auto-publish hook will run on Write. Use this command only when the marker route doesn't fit (existing file you want to publish, HTML from a separate tool).

package/commands/plan.md

@@ -41,8 +41,6 @@ Plan a feature with full validation workflow.
 | Design | `plan` skill | Collaborative design with config discovery |
 | Write | `write-plan` skill | TDD plan with CODE_RULES.md compliance |
 | Review Plan | `review-plan` skill | Validate plan against standards |
-| Execute | `plan-executor` agent | Implement with standards enforcement |
-| Review Code | `readability-review` skill | Validate code before commit |
 
 ## Standards Reference
 

package/commands/review-plan.md

@@ -1,5 +1,5 @@
 Review the current plan against code standards.
 
 1. Identify plan files in `.planning/phases/` or `docs/plans/`
-2. Invoke the `readability-review` skill via the Skill tool with the plan file paths
+2. Review the plan against CODE_RULES.md standards
 3. Report the verdict back to the user