install-hooks
/install-hooks
Instaluje lub naprawia haki sprawdzające sekrety przy commitach, wysyłaniu zmian i działaniach asystenta AI.
- Autor
- gitguardian ↗
- Repozytorium
- agent-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 12
- Skrypty
- 5
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 5 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: evals/files/already-has-hook/setup.sh, evals/files/ambiguous-asks-family/setup.sh, evals/files/global-needs-consent/setup.sh, evals/files/install-claude-code/setup.sh, evals/files/install-precommit-local/setup.sh
Co robi i kiedy
Instaluje lub naprawia haki sprawdzające sekrety przy commitach, wysyłaniu zmian i działaniach asystenta AI.
Oryginalny opis (EN)
Install or repair hooks that check for secrets on each commit, push, or AI assistant action. Use when the user wants leak prevention, when credential-handling work has no hook protection, or when agent scans duplicate a hook that already exists. Use scan-secrets for a one-off scan or a leak investigation.
Jak działa
- Overview
- When to Use
- Onboarding (first use)
- Commands
- Best Practices
- Troubleshooting
Podgląd SKILL.md
--- name: install-hooks description: Install or repair hooks that check for secrets on each commit, push, or AI assistant action. Use when the user wants leak prevention, when credential-handling work has no hook protection, or when agent scans duplicate a hook that already exists. Use scan-secrets for a one-off scan or a leak investigation. license: MIT compatibility: Requires the ggshield CLI installed and authenticated, version 1.49.0 or later for AI-assistant hooks and 1.51.0 or later for codex. Git hooks need git; AI-assistant hooks need the target tool installed. metadata: version: "0.8.0" # x-release-please-version --- # Install secret-scanning hooks ## Overview Hooks do the recurring checks. The agent does not. Never run a scan yourself, and never write a script or other tool to find secrets. Check the existing protection once per context. Reuse protection that works. Offer a missing installation or a repair one time. If the user declines, do not ask again, and do not run scans instead. ## When to Use | Requested protection | Hook | Content that the hook checks | |---|---|---| | Before a commit | `pre-commit` | Staged changes | | Before a push | `pre-push` | Outgoing commits, including intermediate versions | | During AI assistant actions | AI hook for the named or active assistant | Supported prompt and tool events | Use the stage, the assistant, and the scope that the user specified. Ask only for a missing choice. For a bare "install hooks" request, ask which hook family the user wants. An explicit installation request authorizes its stated scope. A recommendation request or a scan request does not authorize an installation. A global installation needs explicit authorization. ## Onboarding (first use) ### Prerequisites Before an installation, check: - `ggshield --version` - the `--help` output of the relevant command - `ggshield api-status` for authentication - the target assistant, when the request names one Do not repeat a check that already passed in this context. ### Setup If the CLI is missing or not authenticated, read [ggshield-cli-setup.md](references/ggshield-cli-setup.md). Otherwise, continue. ## Commands Read the relevant section of [hook-selection.md](references/hook-selection.md) when you check, install, or repair protection. It covers the effective Git hook paths, existing hook managers, and scoped AI hook installation. Do not read it again for a routine operation that it already covered. After an installation, check the configuration. Do not run a test scan. Do not create a test secret, a test commit, or a test push. Report "configured" and "ran and passed" as two different states. The next authorized operation runs the hook and gives the "ran and passed" result. ## Best Practices - Keep existing hook managers and existing secret protection. A hook that only runs a linter is not secret protection. - Do not add manual scans next to a hook. Do not bypass a hook failure. Do not report a skipped or failed check as clean. For an explicit scan, use `scan-secrets` when it is available. - When a hook finds a secret, report the secret type and location. Do not show the secret value. Show the organization's remediation message first, when one exists. Determine if the secret was exposed. A blocked commit or push does not prove that the secret never leaked elsewhere. If the secret is only local, remove it, including from unpushed commits. If the secret was exposed, coordinate a rotation. The same hook checks the next authorized retry. If `scan-secrets` is installed, it contains detailed remediation guidance. ## Troubleshooting If a hook does not run, check the effective hook paths, the hook manager dispatch, the enabled events, the authentication, and the project trust settings. The hook-selection reference describes each check. An AI scan error can let an unscanned action continue. To uninstall, remove only the ggshield entries, through the hook manager that owns them. Keep the other hooks.
Pliki w paczce (12)
- SKILL.md 4 KB
- evals/evals.json 10 KB
- evals/targets.json 1 KB
- evals/files/README.md 4 KB
- evals/files/already-has-hook/setup.sh 2 KB
- evals/files/ambiguous-asks-family/setup.sh 1 KB
- evals/files/global-needs-consent/setup.sh 1 KB
- evals/files/install-claude-code/setup.sh 1 KB
- evals/files/install-precommit-local/setup.sh 1 KB
- references/ggshield-cli-setup.md 14 KB
- references/gitguardian-platform.md 6 KB
- references/hook-selection.md 6 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · gitguardian/agent-skills | 90 | MIT |
| rvdbreemen/adr-kit | 100 | MIT |
| gitguardian/agent-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 7c78a011c274 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90security-secrets-scan
Skanuje repozytorium i artefakty pod kątem wyciekłych kluczy i tokenów, a potem proponuje hooki pre-commit, kontrole CI oraz plan rotacji. - 100scan-secrets
Skanuje pliki, zmiany, commity i obrazy Docker pod kątem zaszytych sekretów, a także bada podejrzany wyciek. Przydaje się przy audytach i kontrolach repozytorium. - 100specstory-guard
Instaluje hook pre-commit skanujący .specstory/history pod kątem sekretów przed commitami, aby chronić historię sesji. - 100secrets-management
Znajduje zaszyte sekrety w kodzie, planuje rotację po wycieku i przenosi sekrety do Vault, AWS, GCP lub Azure. - 100secrets-scan
Wykrywa zaszyte poświadczenia, klucze API i tokeny w kodzie i plikach konfiguracji przed scaleniem lub przy audycie repozytorium. - 100synthesis-git-hooks
Konfiguruje sprawdzanie przy commicie, które blokuje dane logowania, klucze prywatne i niezatwierdzone ujawnienia poza firmę.