Pre-Push Codebase Audit

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/codebase-audit-pre-push

https://github.com/sickn33/antigravity-awesome-skills

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

metadata.json

ORIGIN.md

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

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

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.

1. OS files: .DS_Store, Thumbs.db, desktop.ini
2. Logs: .log, npm-debug.log, yarn-error.log*
3. Temp files: .tmp, .temp, .cache, .swp
4. Build output: dist/, build/, .next/, out/, .cache/
5. Dependencies: nodemodules/, vendor/, pycache_/, *.pyc
6. IDE files: .idea/, .vscode/ (ask user first), *.iml, .project
7. Backup files: .bak, old., backup., _copy.*

Imported Workflow Notes

Imported: Audit Process

1. Clean Up Junk Files

Start by looking for files that shouldn't be on GitHub:

Delete these immediately:

• OS files:

  .DS_Store

  ,

  Thumbs.db

  ,

  desktop.ini

• Logs:

  *.log

  ,

  npm-debug.log*

  ,

  yarn-error.log*

• Temp files:

  *.tmp

  ,

  *.temp

  ,

  *.cache

  ,

  *.swp

• Build output:

  dist/

  ,

  build/

  ,

  .next/

  ,

  out/

  ,

  .cache/

• Dependencies:

  node_modules/

  ,

  vendor/

  ,

  __pycache__/

  ,

  *.pyc

• IDE files:

  .idea/

  ,

  .vscode/

  (ask user first),

  *.iml

  ,

  .project

• Backup files:

  *.bak

  ,

  *_old.*

  ,

  *_backup.*

  ,

  *_copy.*

• Test artifacts:

  coverage/

  ,

  .nyc_output/

  ,

  test-results/

• Personal junk:

  TODO.txt

  ,

  NOTES.txt

  ,

  scratch.*

  ,

  test123.*

Critical - Check for secrets:

• .env

  files (should never be committed)
• Files containing:

  password

  ,

  api_key

  ,

  token

  ,

  secret

  ,

  private_key

• *.pem

  ,

  *.key

  ,

  *.cert

  ,

  credentials.json

  ,

  serviceAccountKey.json

If you find secrets in the code, mark it as a CRITICAL BLOCKER.

2. Fix .gitignore

Check if the

.gitignore

.env.example

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
• Debug statements: remove

  console.log

  ,

  print()

  ,

  debugger

• 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

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

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

• @burp-suite-testing

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @burpsuite-project-parser

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @business-analyst

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @busybox-on-windows

  - 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.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

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.