Skip to content

docs: refresh README and add community health files - #4

Merged
samc621 merged 3 commits into
mainfrom
docs/readme-refresh
Oct 2, 2026
Merged

samc621 merged 3 commits into
mainfrom
docs/readme-refresh

Conversation

@loveneeshdhir

Copy link
Copy Markdown
Contributor

What this changes

A README rewrite for developers meeting Guard for the first time, plus the community files
GitHub uses to show the Contributing, Security and Code of conduct tabs.

README

  • Logo header, badges, and a short nav; the intro is followed by a recording of a real
    install (.github/assets/agenttrail-guard-demo.svg) and then Quick start.
  • Quick start covers every agent's final setup step (including Codex's /hooks
    approval), plus short upgrade and uninstall steps that link to the full reference.
  • New sections: why Guard, how it works, real hook output for deny, ask and warn, the 74
    guardrails by pack with their default actions, how block/ask/warn behave per agent,
    tuning and custom-rule examples (real CLI output), privacy at a glance, a Guard vs OS
    comparison, troubleshooting, and an FAQ.
  • Links to the new product pages (/agenttrail-guard, /agenttrail-os), the install
    guide, Security & Trust, and the --force-reset case study.
  • The collapsed reference sections (install, updating, uninstall, status, rule
    management, scan reports, crash reporting, runtime rules, files kept, and every agent's
    limits) keep their technical content. Changes there are formatting, brand capitalization,
    and one de-duplicated redaction paragraph; the heading "When a guardrail is wrong" is
    now "Managing guardrails".

New files

  • CONTRIBUTING.md: where each report belongs (Guard vs Guardrails), build and test
    steps, CI checks, a code map, and a copy-paste prompt for contributing with a coding agent.
  • SECURITY.md: private reporting to security@agenttrail.sh, and what is and is not in
    scope, based on Guard's documented guarantees.
  • CODE_OF_CONDUCT.md: Contributor Covenant 2.1, with security@agenttrail.sh as the contact.
  • .github/pull_request_template.md: a short checklist matching CI.

None of the new files are in the npm package's files list, so the published package is
unchanged.

How I checked it

  • Every number and behavior in the new sections was checked against the source and the
    bundled @agenttrail/guardrails@0.2.0 catalog: 74 rules, 11 packs, 13 block, 50 ask,
    11 warn; every pack's example commands and the per-agent block/ask/warn behavior were
    run through the real hook.
  • Command output shown in the README was captured from the real CLI, and the recording is
    a real npm install, init --agent claude and status, run against a throwaway config.
  • The README-pinned tests (copy-claims, cli, plugin) pass, and pnpm spell and
    pnpm typecheck are clean. Locally on Windows the suite has pre-existing path and
    line-ending failures that are identical with and without this change; CI on Linux is
    the real check.
  • Every internal anchor and website link resolves.

Follow-ups outside this PR

  • The repository's GitHub About description currently describes AgentTrail OS
    ("traces your agent's execution and automatically compiles repeat failures…"). It
    should be updated to describe Guard, with the website set to
    https://www.agenttrail.sh/agenttrail-guard.

🤖 Generated with Claude Code

Rewrite the README for first-time users: a quick start right after the intro, a
recording of a real install, the 74 guardrails by pack, block/ask/warn behavior per
agent, tuning and custom-rule examples with real CLI output, and links to the Guard
and OS product pages. The detailed reference sections keep their technical content.

Add CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md (Contributor Covenant 2.1) and a
pull request template, so GitHub shows the Contributing, Security and Code of conduct
tabs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
loveneeshdhir and others added 2 commits October 3, 2026 00:28
Point readers of "What Guard catches" to agenttrail.sh/guardrails, where every rule can
be browsed and a command can be checked against the rules.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use colons, semicolons, commas and parentheses instead. Wording is unchanged, and the
real CLI output shown in the README keeps the em dashes the CLI prints.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@samc621 samc621 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@loveneeshdhir thanks, LGTM!

@samc621
samc621 merged commit ea77b1a into main Oct 2, 2026
3 checks passed
github-actions Bot pushed a commit that referenced this pull request Oct 5, 2026
## [0.4.1](v0.4.0...v0.4.1) (2026-10-05)

### Documentation

* **readme:** publish the refreshed README to npm ([378cd7c](378cd7c)), closes [#4](#4) [#6](#6) [#5](#5)

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

🎉 This PR is included in version 0.4.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants