The "everything else" that keeps projects organized
File structure, naming patterns, and project-specific standards that keep code organized
Commit hygiene, branch naming, and PR best practices
Issues that span multiple areas — not security, not performance, but still important
Issues that span multiple domains but don't fit specialized agents
Consistent log levels and formats across the app
Unified error types and reporting patterns
Consistent flag checking and cleanup
Proper i18n key usage and organization
Consistent event naming and properties
Centralized, type-safe configuration
Real examples of project-wide improvements
git commit -m "fix"
git commit -m "updates"
git commit -m "WIP"
git commit -m "asdfasdf"Vague commit messages make history useless
git commit -m "fix(auth): handle expired token refresh"
git commit -m "feat(api): add pagination to users endpoint"
git commit -m "docs: update README with new env vars"
git commit -m "refactor(db): extract query builders"Follow conventional commits for clear history
src/
UserComponent.tsx
userUtils.ts
USER_CONSTANTS.ts
user-types.ts
userApi.tsx # Why .tsx for API?
UserHelpers.tsInconsistent naming and flat structure
src/features/users/
components/
UserCard.tsx
UserList.tsx
hooks/
useUser.ts
api/
users.api.ts
types/
user.types.ts
constants/
user.constants.tsFollow feature-based organization with consistent naming
// Scattered across codebase
const API_URL = process.env.API_URL || 'http://localhost:3000'
// In another file
const apiBase = process.env.NEXT_PUBLIC_API_URL
// In yet another file
if (process.env.NODE_ENV === 'production') {
baseUrl = 'https://api.example.com'
}Environment vars scattered, inconsistent handling
// src/config/env.ts
export const config = {
api: {
baseUrl: requiredEnv('API_URL'),
timeout: optionalEnv('API_TIMEOUT', 5000),
},
features: {
analytics: boolEnv('ENABLE_ANALYTICS', false),
},
} as const
// Usage everywhere
import { config } from '@/config/env'
fetch(config.api.baseUrl + '/users')Centralized config with type-safe access
General Reviewer learns your project's conventions and applies them consistently. It's the agent that makes sure everything fits together.
Understands your project's organization patterns
Validates git practices and PR hygiene
Applies project-specific rules consistently
Load Project Rules
Understands your project's specific conventions and standards
Analyze Changes
Reviews code against project-wide patterns
Check Cross-Cutting
Catches issues that span multiple domains
Suggest Alignment
Helps code fit into the larger project structure
Specialized agents catch specialized issues. General Reviewer catches everything else.
Every file follows the same conventions, making navigation intuitive
Git history that tells a story, not a mess of "fix" commits
Environment and configuration handled consistently everywhere
Specialists handle the deep issues.
General Reviewer handles everything in between.
General Reviewer fills the gaps that specialized agents leave. Free for 14 days, no credit card required.