codebase-audit-pre-push

Audits and fixes codebases for junk files, dead code, security flaws, and scalability issues before GitHub push.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/quinc-dev/qt2026 --skill codebase-audit-pre-push-quinc-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-audit-pre-push
Source: https://github.com/quinc-dev/qt2026/tree/main/.agents/skills/codebase-audit-pre-push
Command: npx skills add https://github.com/quinc-dev/qt2026 --skill codebase-audit-pre-push-quinc-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pushing code to GitHub without a final review risks leaking secrets, shipping dead code, and exposing security vulnerabilities. This Skill performs a line-by-line audit of the entire codebase and fixes issues immediately, so the repository is clean and safe before it goes public. ## Core Features & Use Cases - Junk File & Secret Removal: Deletes OS artifacts, logs, build output, and backup files, and flags hardcoded API keys, passwords, and .env files as critical blockers. - Security & Code Quality Fixes: Detects SQL injection, XSS, weak password hashing, missing auth checks, dead code, unused imports, and debug statements, then repairs them in place. - Scalability & Performance Review: Identifies N+1 queries, missing indexes, unbounded queries, and missing pagination or caching. - Use Case: Before making a side-project repository public, run this Skill to strip secrets, clean up node_modules and .DS_Store files, fix vulnerable dependencies, and receive a scored audit report confirming the repo is ready to push. ## Quick Start Ask the AI to audit this codebase and fix all issues before pushing to GitHub.

Frequently Asked Questions about codebase-audit-pre-push

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

FAQPage Schema
How do I audit my codebase before pushing to GitHub?▼

Run a pre-push audit that scans every file for junk artifacts, dead code, hardcoded secrets, and security vulnerabilities, then fixes them in place. This Skill performs that review and outputs a scored report confirming whether the repository is ready to push.

How to remove secrets and API keys from code before committing?▼

Search the codebase for hardcoded passwords, API keys, tokens, .env files, and credential files like serviceAccountKey.json, then move them into environment variables. Hardcoded secrets are treated as critical blockers that must be fixed before any push.

What files should be deleted before making a repository public?▼

Delete OS files like .DS_Store and Thumbs.db, logs, temp files, build output such as dist/ and .next/, dependencies like node_modules/, IDE folders, backup files, and test artifacts like coverage/. Also verify .gitignore covers all these patterns.

Does this audit check for SQL injection and XSS vulnerabilities?▼

Yes, the security check enforces zero tolerance for injection flaws. It flags string concatenation in SQL queries, exec() with user input, unvalidated file paths, and innerHTML or dangerouslySetInnerHTML usage with user data, then applies fixes.

What are the limitations of an automated pre-push code audit?▼

The audit is not a substitute for environment-specific validation, testing, or expert security review. It should only run when the task matches its scope, and it stops to ask for clarification when inputs, permissions, or success criteria are unclear.