Skip to content

docs: rewrite README guards-first per positioning research (hw-g7p5) - #256

Open
vishnujayvel wants to merge 1 commit into
mainfrom
publish/hw-g7p5
Open

docs: rewrite README guards-first per positioning research (hw-g7p5)#256
vishnujayvel wants to merge 1 commit into
mainfrom
publish/hw-g7p5

Conversation

@vishnujayvel

@vishnujayvel vishnujayvel commented Jul 12, 2026

Copy link
Copy Markdown
Owner

Factory-authored (bead hw-g7p5, convoy readme-relaunch). Rewrites the README to lead with the guardrails & policy engine story per the 2026-07-11 positioning research: hero = blocked-dangerous-command example + the YAML guard rule; cost analytics + feed-daemon status line as flagship features; honest maturity labels on TUI (early), coaching (narrow), notifications (experimental — Anthropic ships native push since v2.1.110). Every claim cross-checked against the shipped command surface per the bead's V1 accuracy gate. (Published as a single squashed commit: the two mirror commits cherry-pick-conflict against GitHub's squash history; file content is identical to the factory's final state 406e3f8.)

DO NOT MERGE until Vishnu reviews — outward-facing marketing copy, human review gate per the bead brief.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EjWqH4FMkdczkSagzXw3dQ

Summary by CodeRabbit

  • Documentation
    • Repositioned the product around guardrails and policy enforcement for Claude Code.
    • Clarified command-blocking behavior, rule evaluation, configuration, and fail-open handling.
    • Expanded onboarding guidance for setup, safety audits, backups, dry runs, and removal.
    • Added or refreshed documentation for cost analytics, budgets, live status feeds, health checks, testing, recipes, and security.
    • Updated configuration examples, comparison tables, navigation links, and product messaging.

@github-actions

Copy link
Copy Markdown
Warnings
⚠️

No issue reference found in PR description. Add Closes #XX or No issue.

Generated by 🚫 dangerJS against a74b54e

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

README.md is repositioned around Claude Code guardrails and policy evaluation, with expanded operational documentation for wiring, analytics, status feeds, health checks, configuration, testing, security, maturity, navigation, and project messaging.

Changes

README refresh

Layer / File(s) Summary
Guard positioning and semantics
README.md
Introduces guard and policy-engine messaging, explicit guard semantics, revised onboarding language, and updated comparison entries.
Operations and execution documentation
README.md
Documents hookwise init --wire, cost analytics, status feeds, setup health checks, configuration behavior, and the three-phase execution engine.
Configuration, maturity, and navigation references
README.md
Refreshes testing, recipes, maturity, security, documentation navigation, and footer text.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description covers summary and motivation, but omits the required test plan and checklist sections from the template. Add the missing Test plan and Checklist sections, and include concrete verification steps and completed checklist items.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly matches the main change: rewriting the README around guardrails and policy-engine positioning.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch publish/hw-g7p5

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 64: Revise the README sentence around “With hookwise” so it states that
hookwise reads and evaluates hookwise.yaml, while Claude Code only supplies tool
calls, receives results, and can help author rules. Avoid implying Claude Code
natively reads or supports the YAML without hookwise.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 41ced524-7761-4563-822b-e6d3b58e5c96

📥 Commits

Reviewing files that changed from the base of the PR and between 0a488f0 and a74b54e.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
```

One file. Claude Code reads it, understands it, and can even help you write new rules. No bash scripts to debug.
With hookwise: add a rule, remove a rule, done. Claude Code reads the YAML, understands it, and can even help you write new rules.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Clarify which component reads the policy.

hookwise loads and evaluates hookwise.yaml; Claude Code supplies the tool call and receives the result. Saying Claude Code “reads the YAML” may imply native support and cause users to expect this to work without hookwise wiring. Reword this to say hookwise reads the YAML, while Claude Code can help author it.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 64, Revise the README sentence around “With hookwise” so
it states that hookwise reads and evaluates hookwise.yaml, while Claude Code
only supplies tool calls, receives results, and can help author rules. Avoid
implying Claude Code natively reads or supports the YAML without hookwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant