phase-1-foundation-weeks-1-4

Enforce pre-commit secrets checks and branch protection across repositories.

3|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill phase-1-foundation-weeks-1-4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-1-foundation-weeks-1-4
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/enforce/skills/phase-1-foundation-weeks-1-4
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill phase-1-foundation-weeks-1-4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, jq, and includes scripts (resource) components.

What problem does it solve?

Phase 1 establishes the foundation of SDLC security through two critical control layers: pre-commit hooks to block insecure changes locally before commits, and branch protection to prevent unauthorized merges at the repository level. These controls work together to create defense-in-depth at the source code level.

Core Features & Use Cases

  • Pre-commit security gates to catch secrets and enforce code quality before commits.
  • Branch protection enforcement to require reviews and signed commits across repositories.
  • Organization-wide distribution strategies to apply policies consistently across teams and repos.

Quick Start

Enable the pre-commit hooks and branch protection policies across your repositories using the implementation roadmap.

Frequently Asked Questions about phase-1-foundation-weeks-1-4

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

FAQPage Schema
How do I enforce pre-commit secrets detection across multiple repositories?

Pre-commit secrets detection across multiple repositories is enforced by applying organization-wide distribution strategies that block insecure changes locally before commits are made.

What is branch protection and how does it secure the SDLC?

Branch protection secures the SDLC by requiring code reviews and commit-signature verification at the repository level, preventing unauthorized merges into protected main branches.

Do I need git and gh installed to set up commit-signature verification and branch protection?

Yes, git, gh, and jq are required dependencies to automate branch protection enforcement, commit-signature verification, and policy validation across your organizational workflows.

Can I apply pre-commit hooks and branch protection policies consistently across an entire organization?

Yes, pre-commit hooks and branch protection policies can be distributed consistently across an organization using strategies that ensure all teams and repositories enforce secure code audits.

What is the best way to block insecure code changes before they reach a protected branch?

The best way to block insecure changes is combining pre-commit security gates to catch secrets locally with repository-level branch protection to prevent unauthorized merges.

Why does my organization need both pre-commit hooks and branch protection for SDLC security?

Pre-commit hooks and branch protection create defense-in-depth at the source code level by catching secrets locally before commits and preventing unauthorized merges at the repository level.