production-code-audit
Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
Install
npx skills add https://github.com/sickn33/agentic-awesome-skills --skill production-code-auditSKILL.md
Production Code Audit
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use This Skill
- Use when user says "make this production-ready"
- Use when user says "audit my codebase"
- Use when user says "make this professional/corporate-level"
- Use when user says "optimize everything"
- Use when user wants enterprise-grade quality
- Use when preparing for production deployment
- Use when code needs to meet corporate standards
Examples
Example 1: Autonomous Codebase Transformation
User: @production-code-audit make this production-ready
AI: I'll scan your entire codebase and transform it to production-grade quality.
**Phase 1: Discovering Codebase** (analyzing 247 files)
- Detected: Node.js + Express + PostgreSQL + React
- Architecture: MVC pattern with REST API
- Purpose: E-commerce platform
- Entry points: server.js, src/index.tsx
**Phase 2: Scanning for Issues** (line-by-line analysis)
Found 127 issues:
- š“ CRITICAL: 8 issues
- š HIGH: 23 issues
- š” MEDIUM: 41 issues
- šµ LOW: 55 issues
**Phase 3: Fixing Issues Automatically**
š“ CRITICAL FIXES (8/8 completed):
1. ā
Fixed SQL injection in UserRepository.findByEmail()
- Before: String concatenation in query
- After: Parameterized query with $1 placeholder
2. ā
Removed hardcoded database password from config/database.ts
- Before: password: 'SuperSecret123!'
- After: password: process.env.DB_PASSWORD
3. ā
Added authentication to admin routes
- Before: No auth middleware
- After: authenticateToken + requireRole('admin')
4. ā
Fixed weak password hashing (MD5 ā bcrypt)
- Before: crypto.createHash('md5')
- After: bcrypt.hash(password, 12)
5. ā
Fixed circular dependency: OrderService ā PaymentService
- Before: Direct imports causing cycle
- After: Event-based decoupling with EventBus
6. ā
Added input validation to all API endpoints
- Before: No validation
- After: Zod schemas validating all inputs
7. ā
Fixed authentication bypass in auth middleware
- Before: next() called on missing token
- After: Returns 401 error
8. ā
Fixed mass assignment vulnerability in UserController
- Before: Accepts all fields from req.body
- After: Whitelist of allowed fields only
š HIGH PRIORITY FIXES (23/23 completed):
9. ā
Fixed N+1 query in OrderService.getOrdersWithItems()
- Before: Loop with individual queries (2.8s)
- After: Single query with joins (45ms)
- Performance: 98% improvement
10. ā
Refactored UserService god class (850 lines ā 4 focused services)
- UserAuthenticationService (login, logout, password)
- UserProfileService (CRUD operations)
- UserNotificationService (email, SMS)
- UserPermissionService (roles, permissions)
11. ā
Added Redis caching for product queries
- Before: Database query every request
- After: Cache with 1-hour TTL
- Performance: 95% faster
12. ā
Optimized bundle size
- Before: 850KB (gzipped: 280KB)
- After: 380KB (gzipped: 120KB)
- Improvement: 55% reduction
13. ā
Added database indexes
- orders(user_id, status, created_at)
- products(category, price)
- Query performance: 98% improvement
[... 11 more high-priority fixes ...]
š” MEDIUM PRIORITY FIXES (41/41 completed):
[... all medium fixes ...]
šµ LOW PRIORITY IMPROVEMENTS (55/55 completed):
[... all low improvements ...]
**Phase 4: Adding Production Infrastructure**
ā
Added structured logging (Winston)
ā
Added error tracking (Sentry)
ā
Added health check endpoints (/health, /ready)
ā
Added monitoring (Prometheus metrics)
ā
Added rate limiting (Redis-based)
ā
Added API documentation (Swagger/OpenAPI)
ā
Added comprehensive README
ā
Added deployment guide
ā
Added CI/CD pipeline (.github/workflows)
**Phase 5: Verification**
ā
All tests passing (1,247 tests)
ā
Test coverage: 42% ā 87%
ā
Security scan: 0 vulnerabilities
ā
Performance: API response time 3.2s ā 180ms
ā
Bundle size: 850KB ā 380KB
ā
Lighthouse score: 62 ā 94
**TRANSFORMATION COMPLETE**
Your codebase is now production-ready with enterprise-grade quality:
š Metrics:
- Issues fixed: 127/127 (100%)
- Test coverage: 87% (target: 80%+)
- API performance: 94% improvement
- Security: OWASP Top 10 compliant
- Code quality: Grade A-
š Files changed: 89 files
š Lines changed: +3,247 / -1,892
š Ready for production deployment!
Example 2: Automatic Security Hardening
User: @production-code-audit secure this codebase
AI: Scanning for security vulnerabilities...
**Security Scan Complete**
Found 15 security issues:
- š“ CRITICAL: 5
- š HIGH: 7
- š” MEDIUM: 3
**Fixing all security issues automatically...**
š“ CRITICAL (5/5 fixed):
1. ā
SQL Injection in UserRepository
\`\`\`typescript
// Before (VULNERABLE)
const query = \`SELECT * FROM users WHERE email = '\${email}'\`;
// After (SECURE)
const query = 'SELECT * FROM users WHERE email = $1';
await db.query(query, [email]);
\`\`\`
2. ā
Hardcoded Secrets Removed
\`\`\`typescript
// Before (INSECURE)
const tokenSigningKey = '[redacted weak value]';
// After (SECURE)
const JWT_SECRET = process.env.JWT_SECRET;
if (!JWT_SECRET) throw new Error('JWT_SECRET required');
\`\`\`
3. ā
Authentication Added to Admin Routes
\`\`\`typescript
// Before (VULNERABLE)
router.delete('/api/admin/users/:id', deleteUser);
// After (SECURE)
router.delete('/api/admin/users/:id',
authenticateToken,
requireRole('admin'),
deleteUser
);
\`\`\`
4. ā
Password Hashing Upgraded
\`\`\`typescript
// Before (WEAK)
const hash = crypto.createHash('md5').update(password).digest('hex');
// After (STRONG)
const hash = await bcrypt.hash(password, 12);
\`\`\`
5. ā
Input Validation Added
\`\`\`typescript
// Before (VULNERABLE)
const user = await db.user.create({ data: req.body });
// After (SECURE)
const schema = z.object({
email: z.string().email(),
password: z.string().min(12),
name: z.string().min(2).max(100)
});
const validated = schema.parse(req.body);
const user = await db.user.create({ data: validated });
\`\`\`
**Security Status:**
- ā
OWASP Top 10: Compliant
- ā
SQL Injection: Protected
- ā
XSS: Protected
- ā
CSRF: Protected
- ā
Authentication: Secure
- ā
Secrets: Environment variables
- ā
Dependencies: No vulnerabilities
š Codebase is now secure and production-ready!
Example 3: Performance Optimization
User: @production-code-audit optimize performance
AI: Analyzing performance bottlenecks...
**Performance Analysis Complete**
Current metrics:
- API response time: 3.2s (target: <200ms)
- Page load time: 8.5s (target: <2s)
- Bundle size: 850KB (target: <200KB)
**Optimizing automatically...**
ā
Fixed N+1 queries (3.2s ā 180ms - 94% faster)
ā
Added Redis caching (95% cache hit rate)
ā
Optimized database indexes (98% faster queries)
ā
Reduced bundle size (850KB ā 380KB - 55% smaller)
ā
Optimized images (28MB ā 3.2MB - 89% smaller)
ā
Implemented code splitting
ā
Added lazy loading
ā
Parallelized async operations
**Performance Results:**
| Metric | Before | After | Improvement |
|--------|--------|-------|-------------|
| API Response | 3.2s | 180ms | 94% |
| Page Load | 8.5s | 1.8s | 79% |
| Bundle Size | 850KB | 380KB | 55% |
| Image Size | 28MB | 3.2MB | 89% |
| Lighthouse | 42 | 94 | +52 points |
š Performance optimized to production standards!
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.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".