repo-sentinel

Audit Git repositories for security and public-release readiness across attack surfaces.

310|45|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Mathews-Tom/praxis-skills --skill repo-sentinel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-sentinel
Source: https://github.com/Mathews-Tom/praxis-skills/tree/main/skills/repo-sentinel
Command: npx skills add https://github.com/Mathews-Tom/praxis-skills --skill repo-sentinel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents accidental or unnoticed exposure of sensitive data and internal topology when making a repository public by defining what belongs in a public repo, detecting violations across multiple attack surfaces, and prescribing safe remediation and enforcement steps.

Core Features & Use Cases

  • Comprehensive Attack-Surface Audit: Scans git history, source code, docs, config, .gitignore, CI/CD, containers/IaC, dependencies/lock files, binaries, metadata, platform-specific (GitHub/GitLab), license, and community files.
  • Fast-Path and Full Audits: Offers a quick staged-change check for pre-push validation and a full 20+ check pre-release audit with severity-classified findings.
  • Enforcement & Remediation: Provides templates and procedures for pre-commit hooks, CI gates, .gitignore generation, history scrubbing, and credential rotation guidance.
  • Use Case: Run before first public push or release to ensure no secrets, internal URLs, private registry references, or license issues are present and to configure continuous prevention controls.

Quick Start

Run a full repo audit and produce a severity-classified remediation plan for public release readiness.

Frequently Asked Questions about repo-sentinel

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

FAQPage Schema
How do I check a git repository for secrets before making it public?

A full pre-release audit scans git history, source code, and config files for secrets, producing severity-classified findings and prescriptive remediation steps to ensure public-release readiness.

What is included in a pre-release repository security audit?

A pre-release security audit scans git history, source code, CI/CD pipelines, containers, IaC, dependencies, and metadata to detect exposed secrets, internal URLs, and license issues across all repository attack surfaces.

How do I set up pre-commit hooks to prevent committing secrets?

You can prevent committing secrets by configuring pre-commit hooks and CI gates using provided templates, validating staged changes to block sensitive data exposure before pushing to the repository.

Can I use trufflehog or gitleaks for scanning my repository?

Yes, this audit process supports optional integrations with trufflehog or gitleaks to enhance secret detection capabilities during pre-release audits and push-time validations.

How do I scrub git history to remove exposed credentials?

To scrub git history and remove exposed credentials, follow the history-scrub guidance and credential rotation procedures provided alongside severity-classified findings after detecting security violations.

Does the audit check GitHub and GitLab specific configuration files?

Yes, the audit includes platform-specific checks for GitHub and GitLab configuration files to detect internal topology exposure, private registry references, and platform-specific security misconfigurations.