Repository navigation
Lead the README with the security guardrails each plugin ships - #9
jothimani-rajendran wants to merge 1 commit into
Conversation
Rework README.md around what the packages here refuse in this client: a security-first header with badges, the refreshed hero GIF, a "What these plugins refuse" table grouped by security area (only packages published here, marked guard, gate or advisory, with catalog eval counts), the advisory and not-yet-packaged policies in collapsible lists, the client's own hook behaviour and fail-open notes, a family table linking every sibling plugin repository, and concrete upstream contribution routes. Install steps and every client-specific claim about witnessed or documented blocking are kept verbatim. The five plugin repositories now share one README structure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No fix fits inside this PR. The generated tree should only change through the Publish workflow ( Generated by Claude Code |
|
Closing at the owner's request (2026-10-05). The README refresh will be redone once before launch, so that it matches the chock.sh site and the current labels. Generated by Claude Code |
What
Reworks
README.md(hand-written, not generated) so it leads with security:PreToolUse, gates onStoponly. Each row has its catalog eval-case count. The 12 advisory packages and the catalog policies not packaged here are in collapsible lists.Install steps are unchanged. This PR matches the structure of the sibling PRs in the claude, copilot, cursor and devin plugin repos.
Why README.md is safe to edit here
The generator writes the packages and
PLUGINS.md, notREADME.md. A test regeneration with chock 0.15.0 left the README unchanged.close-prs.ymlonly closes PRs from forks.Checks
README.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01LAxde3s5KW8N36kS8LF3er
Generated by Claude Code