origin-vibe-security-setup

Configures git hooks, gitleaks scanning, and agent bypass rules for repository security guardrails.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Aki2022/skills --skill origin-vibe-security-setup-aki2022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: origin-vibe-security-setup
Source: https://github.com/Aki2022/skills/tree/main/origin-vibe-security-setup
Command: npx skills add https://github.com/Aki2022/skills --skill origin-vibe-security-setup-aki2022

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding repositories risk leaking secrets, local paths, and credentials through commits and pushes, and developers often bypass security checks when blocked. This Skill sets up reproducible vibe-guard guardrails so hooks and CI checks enforce security without being disabled. ## Core Features & Use Cases - Guardrail Bootstrapping: Runs vibe-guard doctor and vibe-guard repo-bootstrap to generate AGENTS.md, SECURITY.md, and CI workflow files. - Secret and Local-Info Detection: Configures gitleaks secret scanning and detection of local paths, personal emails, and tokens in commits. - Agent Bypass Prevention: Enforces rules against --no-verify commits, hook rewrites, and removing security workflows. - Use Case: A developer's commit is blocked by a secret-scanning hook; use this Skill to diagnose the root cause and remediate it properly instead of bypassing the check. ## Quick Start Ask the AI to set up vibe-guard security guardrails for this repository and verify the hooks are active.

Frequently Asked Questions about origin-vibe-security-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up git pre-commit hooks for secret scanning?

Run vibe-guard doctor to check global setup, then vibe-guard repo-bootstrap to generate hooks and config files. The bootstrap creates gitleaks-based secret scanning plus AGENTS.md, SECURITY.md, and a CI workflow.

What should I do when a security hook blocks my git commit?

Fix the root cause of the blocked commit rather than bypassing it. Never use git commit --no-verify or -n; only add a narrow allowlist rule after human review of the finding.

Does vibe-guard work with CI pipelines like GitHub Actions?

Yes, repo-bootstrap generates a .github/workflows/vibe-guard.yml file so the same checks run in CI. The skill forbids removing security workflows just to make CI pass.

What sensitive data does the guardrail detect in commits?

It detects secrets via gitleaks plus local paths, personal emails, credentials, private URLs, drive names, and tokens. These are blocked from code, docs, PRs, issues, logs, and commit messages.

When should I not bypass a failed pre-push check?

Never bypass failed hooks or CI checks under this skill's rules. Diagnose the failure, remediate the underlying issue, and only add a scoped allowlist exception after human review.