claude

privacy-guard

Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external contributors and in CI while gitleaks still covers generic secrets.

72 on GitHubby Francesco Vadicamov1.3.3MITupdated 2 months ago
/

Plugin privacy-guard from marketplace dev-agent-skills in fvadicamo/dev-agent-skills. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (1)

  • privacy-guard

    Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-publ

View source on GitHub

More from fvadicamo/dev-agent-skills

All 5 plugins →

Git commit, PR creation, review, and merge skills following Conventional Commits

4 skills

72

Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of against a published spec it may never have adopted. Ships the decision-records skill: a propose-then-write flow that never rewrites an accepted record, and check-decisions.sh, a validator that deduces the filename scheme, section set and status vocabulary from the records already present and reports eight classes of violation with a stable code and an exit status. Ships no template into the target repo, and delegates private-token scanning to privacy-guard rather than keeping a second denylist.

1 skill

72

Safety guardrails for running Claude Code with reduced supervision. The guard-destructive PreToolUse hook matches against a normalized view of each command (heredoc bodies and comments stripped, quoted strings neutralized except interpreter arguments like ssh / sh -c / eval / su / doas), so a command that merely mentions a destructive pattern is not flagged. It hard-blocks catastrophic Bash commands (rm -rf /, rsync --delete, docker volume rm) and makes rm/rmdir scope-aware: operations whose operands all resolve inside the allowed workspace (the session project root, temp dirs, any $GUARD_ALLOWED_EXTRA root, or a variable assigned from a bare mktemp earlier in the same command) run silently, while anything outside it (or any glob/variable/escape it cannot resolve) raises a single reflective confirmation. git reset --hard / clean / restore, shred, dd, mkfs still always prompt.

hooks

72

Guide for creating Claude Code skills following Anthropic's best practices

1 skill

72

Maintain privacy-guard?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins5 plugins