Skip to content

fvadicamo/dev-agent-skills / plugins/privacy-guard/skills/privacy-guard

privacy-guard

Verified

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-public repo, before commits or releases, when writing deployment docs for an OSS project, or when the user asks to "set up the privacy guard", "install privacy-guard", "check for leaks", "protect this public repo". Bootstraps a pre-commit hook backed by a gitignored local denylist plus gitleaks.

FileKindSize
SKILL.mdskill md10.2 KB
references/check-sync.shexecutablescript3.1 KB
references/check_privacy.shexecutablescript6.1 KB
references/denylist-template.txtmarkdown1.3 KB
references/pre-commit-snippet.yamlconfig620 B

references/check-sync.sh

View on GitHub
#!/usr/bin/env bash
# Are a repo's materialized copies of check_privacy.sh current with this skill?
#
#   check-sync.sh REPO...        (exit 0 all current, 1 any divergence, 2 usage)
#
# check_privacy.sh is COPIED into each repo on purpose: the repo has to stand on its own
# for external contributors and CI, which do not have this plugin installed. The cost of
# copying is drift, and drift here is invisible: a copy that is a month behind looks
# exactly like a current one. Observed, which is why this exists and why the copies carry
# a version line in their header.
#
# Copies are asked to GIT, not to the filesystem: `ls-files` answers "what this repo
# ships", which is the question, and it answers it wherever the copy lives. A hardcoded
# scripts/check_privacy.sh would be a second place to keep in sync with the first.

set -uo pipefail

if [ "$#" -eq 0 ]; then
    echo "Usage: $0 REPO..." >&2
    exit 2
fi

CANONICAL="$(cd "$(dirname "$0")" && pwd)/check_privacy.sh"
if [ ! -f "$CANONICAL" ]; then
    echo "check-sync.sh: canonical copy not found next to this script ($CANONICAL)." >&2
    echo "Nothing was compared: a silent pass here would read as 'everything is current'." >&2
    exit 2
fi

# `# check_privacy.sh 1.1.1 -- canonical copy: ...` -> `1.1.1`, empty if the line is absent
# (a copy older than the version line itself, which is the drift this was built for).
versione() {
    sed -n 's/^# check_privacy\.sh \([0-9][0-9.]*\) --.*/\1/p' "$1" | head -1
}

vc="$(versione "$CANONICAL")"
status=0

for repo in "$@"; do
    if ! git -C "$repo" rev-parse --git-dir >/dev/null 2>&1; then
        echo "SKIP     $repo: not a git repository"
        status=1
        continue
    fi
    trovate=0
    while IFS= read -r rel; do
        [ -n "$rel" ] || continue
        trovate=$((trovate + 1))
        copia="$repo/$rel"
        vr="$(versione "$copia")"
        if cmp -s "$CANONICAL" "$copia"; then
            echo "OK       $repo/$rel (${vc:-no version})"
        elif [ -z "$vr" ]; then
            echo "BEHIND   $repo/$rel: no version line, predates ${vc:-the canonical copy}. Recopy."
            status=1
        elif [ "$vr" != "$vc" ]; then
            echo "BEHIND   $repo/$rel: $vr, canonical is $vc. Recopy."
            status=1
        else
            # Stessa versione, byte diversi: qualcuno ha modificato la copia. E' il caso
            # peggiore, perche' la versione dichiara "sono aggiornato" e non lo e': la
            # modifica va portata a monte, o il sync successivo la cancella in silenzio.
            echo "DIVERGED $repo/$rel: version $vr but content differs. Take the change"
            echo "         upstream and recopy, or the next sync silently reverts it:"
            diff -u "$CANONICAL" "$copia" | sed -n '4,13p' | sed 's/^/         /'
            status=1
        fi
    done < <(git -C "$repo" ls-files -- '*check_privacy.sh' 2>/dev/null)
    if [ "$trovate" -eq 0 ]; then
        echo "NONE     $repo: ships no check_privacy.sh (guard installed another way, or not"
        echo "         installed). Said out loud because silence here would read as 'current'."
    fi
done

exit "$status"
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall