Pre-Push Codebase Audit workflow skill. Use this skill when the user needs Deep audit before GitHub push: removes junk files, dead code, security holes, and optimization issues. Checks every file line-by-line for production readiness and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
مستكشف الملفات
3 ملفات
عرض SKILL.md
SKILL.md
تعليمات المصدر · معاينة للقراءة فقط
name
codebase-audit-pre-push
description
Pre-Push Codebase Audit workflow skill. Use this skill when the user needs Deep audit before GitHub push: removes junk files, dead code, security holes, and optimization issues. Checks every file line-by-line for production readiness and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/codebase-audit-pre-push from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Pre-Push Codebase Audit As a senior engineer, you're doing the final review before pushing this code to GitHub. Check everything carefully and fix problems as you find them.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Your Job, Output Format, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
User requests "audit the codebase" or "review before push"
Before making the first push to GitHub
Before making a repository public
Pre-production deployment review
User asks to "clean up the code" or "optimize everything"
Use when the request clearly matches the imported source intent: Deep audit before GitHub push: removes junk files, dead code, security holes, and optimization issues. Checks every file line-by-line for production readiness.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
If you find secrets in the code, mark it as a CRITICAL BLOCKER.
2. Fix .gitignore
Check if the .gitignore file exists and is thorough. If it’s missing or not complete, update it to include all junk file patterns above. Ensure that .env.example exists with keys but no values.
3. Audit Every Source File
Look through each code file and check:
Dead Code (remove immediately):
Commented-out code blocks
Unused imports/requires
Unused variables (declared but never used)
Unused functions (defined but never called)
Unreachable code (after return, inside if (false))
Duplicate logic (same code in multiple places—combine)
Code Quality (fix issues as you go):
Vague names: data, info, temp, thing → rename to be descriptive
Magic numbers: if (status === 3) → extract to named constant
TODO/FIXME comments: either resolve them or delete them
TypeScript any: add proper types or explain why any is used
Use === instead of == in JavaScript
Functions longer than 50 lines: consider splitting
Nested code greater than 3 levels: refactor with early returns
Logic Issues (critical):
Missing null/undefined checks
Array operations on potentially empty arrays
Async functions that are not awaited
Promises without .catch() or try/catch
Possibilities for infinite loops
Missing default in switch statements
4. Security Check (Zero Tolerance)
Secrets: Search for hardcoded passwords, API keys, and tokens. They must be in environment variables.
Injection vulnerabilities:
SQL: No string concatenation in queries—use parameterized queries only
Command injection: No exec() with user-provided input
Path traversal: No file paths from user input without validation
XSS: No innerHTML or dangerouslySetInnerHTML with user data
Auth/Authorization:
Passwords hashed with bcrypt/argon2 (never MD5 or plain text)
Protected routes check for authentication
Authorization checks on the server side, not just in the UI
No IDOR: verify users own the resources they are accessing
Data exposure:
API responses do not leak unnecessary information
Error messages do not expose stack traces or database details
Pagination is present on list endpoints
Dependencies:
Run npm audit or an equivalent tool
Flag critically outdated or vulnerable packages
5. Scalability Check
Database:
N+1 queries: loops with database calls inside → use JOINs or batch queries
Missing indexes on WHERE/ORDER BY columns
Unbounded queries: add LIMIT or pagination
Avoid SELECT *: specify columns
API Design:
Heavy operations (like email, reports, file processing) → move to a background queue
Rate limiting on public endpoints
Caching for data that is read frequently
Timeouts on external calls
Code:
No global mutable state
Clean up event listeners (to avoid memory leaks)
Stream large files instead of loading them into memory
6. Architecture Check
Organization:
Clear folder structure
Files are in logical locations
No "misc" or "stuff" folders
Separation of concerns:
UI layer: only responsible for rendering
Business logic: pure functions
Data layer: isolated database queries
No 500+ line "god files"
Reusability:
Duplicate code → extract to shared utilities
Constants defined once and imported
Types/interfaces reused, not redefined
7. Performance
Backend:
Expensive operations do not block requests
Batch database calls when possible
Set cache headers correctly
Frontend (if applicable):
Implement code splitting
Optimize images
Avoid massive dependencies for small utilities
Use lazy loading for heavy components
8. Documentation
README.md must include:
Description of what the project does
Instructions for installation and execution
Required environment variables
Guidance on running tests
Code comments:
Explain WHY, not WHAT
Provide explanations for complex logic
Avoid comments that merely repeat the code
9. Testing
Critical paths should have tests (auth, payments, core features)
No test.only or fdescribe should remain in the code
Avoid test.skip without an explanation
Tests should verify behavior, not implementation details
10. Final Verification
After making all changes, run the app. Ensure nothing is broken. Check that:
The app starts without errors
Main features work
Tests pass (if they exist)
No regressions have been introduced
Imported: Your Job
Review the entire codebase file by file. Read the code carefully. Fix issues right away. Don't just note problems—make the necessary changes.
Examples
Example 1: Ask for the upstream workflow directly
Use @codebase-audit-pre-push to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @codebase-audit-pre-push against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @codebase-audit-pre-push for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @codebase-audit-pre-push using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Read the code thoroughly, don't skim
Fix issues immediately, don’t just document them
If uncertain about removing something, ask the user
Test after making changes
Be thorough but practical—focus on real problems
Security issues are blockers—nothing should ship with critical vulnerabilities
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Imported Operating Notes
Imported: Key Principles
Read the code thoroughly, don't skim
Fix issues immediately, don’t just document them
If uncertain about removing something, ask the user
Test after making changes
Be thorough but practical—focus on real problems
Security issues are blockers—nothing should ship with critical vulnerabilities
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/codebase-audit-pre-push, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Output Format
After auditing, provide a report:
CODEBASE AUDIT COMPLETE
FILES REMOVED:
- node_modules/ (build artifact)
- .env (contained secrets)
- old_backup.js (unused duplicate)
CODE CHANGES:
[src/api/users.js]
✂ Removed unused import: lodash
✂ Removed dead function: formatOldWay()
🔧 Renamed 'data' → 'userData' for clarity
🛡 Added try/catch around API call (line 47)
[src/db/queries.js]
⚡ Fixed N+1 query: now uses JOIN instead of loop
SECURITY ISSUES:
🚨 CRITICAL: Hardcoded API key in config.js (line 12) → moved to .env
⚠️ HIGH: SQL injection risk in search.js (line 34) → fixed with parameterized query
SCALABILITY:
⚡ Added pagination to /api/users endpoint
⚡ Added index on users.email column
FINAL STATUS:
✅ CLEAN - Ready to push to GitHub
Scores:
Security: 9/10 (one minor header missing)
Code Quality: 10/10
Scalability: 9/10
Overall: 9/10
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
