omgkit 2.18.0 → 2.19.0

package/README.md

@@ -426,24 +426,34 @@ omgkit help         # Show help
 
 ## ✅ Before-Commit Validation
 
-OMGKIT enforces strict quality standards with **4800+ automated tests**:
+OMGKIT provides two types of before-commit rules:
+
+| Rule Type | Location | Purpose |
+|-----------|----------|---------|
+| **OMGKIT Internal** | `plugin/stdrules/omgkit/` | For OMGKIT contributors |
+| **Project Rules** | `.omgkit/stdrules/BEFORE_COMMIT.md` | For your projects |
+
+### For OMGKIT Contributors
 
 ```bash
-npm test    # Run all validation tests before commit
+npm test    # Run all 4800+ validation tests
 ```
 
-### Quality Gates
-
 | Category | Requirement |
 |----------|-------------|
 | **Agents** | 50+ lines, valid frontmatter, skills/commands arrays |
 | **Commands** | 15+ lines, description, registered as slash command |
 | **Skills** | 30+ lines, name/description if frontmatter present |
 | **Workflows** | 50+ lines, description, agents array |
-| **Registry** | Version sync, cross-reference validation |
-| **Content** | No placeholder text (TODO:, FIXME:, etc.) |
 
-All commands must be registered in `registry.yaml` under valid namespaces.
+### For Project Developers
+
+When you run `omgkit init`, a comprehensive `BEFORE_COMMIT.md` is created with:
+- Code quality checks
+- Git commit standards
+- Security guidelines
+- Documentation requirements
+
 See [full documentation](https://omgkit.mintlify.app/resources/before-commit).
 
 ## 📁 Project Structure
@@ -463,6 +473,7 @@ your-project/
 │   ├── logs/            # Activity logs
 │   ├── devlogs/         # Development logs, planning, tracking (git-ignored)
 │   └── stdrules/        # Standards & rules for the project
+│       ├── BEFORE_COMMIT.md   # Before-commit checklist
 │       └── SKILL_STANDARDS.md
 └── OMEGA.md             # Project context
 ```

package/lib/cli.js

@@ -395,7 +395,8 @@ export function initProject(options = {}) {
     { src: 'settings.json', dest: '.omgkit/settings.json' },
     { src: 'devlogs/README.md', dest: '.omgkit/devlogs/README.md' },
     { src: 'stdrules/README.md', dest: '.omgkit/stdrules/README.md' },
-    { src: 'stdrules/SKILL_STANDARDS.md', dest: '.omgkit/stdrules/SKILL_STANDARDS.md' }
+    { src: 'stdrules/SKILL_STANDARDS.md', dest: '.omgkit/stdrules/SKILL_STANDARDS.md' },
+    { src: 'stdrules/BEFORE_COMMIT.md', dest: '.omgkit/stdrules/BEFORE_COMMIT.md' }
   ];
 
   templates.forEach(({ src, dest }) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omgkit",
-  "version": "2.18.0",
+  "version": "2.19.0",
   "description": "Omega-Level Development Kit - AI Team System for Claude Code. 33 agents, 111 commands, 127 skills, 49 workflows.",
   "keywords": [
     "claude-code",

package/plugin/registry.yaml

@@ -1,15 +1,15 @@
 # OMGKIT Component Registry
 # Single Source of Truth for Agents, Skills, Commands, Workflows, and MCPs
-# Version: 2.18.0
+# Version: 2.19.0
 # Updated: 2026-01-02
 
-version: "2.17.0"
+version: "2.19.0"
 
 # =============================================================================
 # OPTIMIZED ALIGNMENT PRINCIPLE (OAP)
 # =============================================================================
 # Core architectural rule defining component relationships.
-# See: plugin/stdrules/ALIGNMENT_PRINCIPLE.md for full documentation.
+# See: plugin/stdrules/omgkit/ALIGNMENT_PRINCIPLE.md for full documentation.
 #
 # Hierarchy (lower levels are used by higher levels):
 #   Level 0: MCPs       → Foundation layer
@@ -29,7 +29,7 @@ version: "2.17.0"
 alignment_principle:
   version: "1.0.0"
   enforced: true
-  documentation: "plugin/stdrules/ALIGNMENT_PRINCIPLE.md"
+  documentation: "plugin/stdrules/omgkit/ALIGNMENT_PRINCIPLE.md"
   hierarchy:
     - level: 0
       type: mcp

package/templates/stdrules/BEFORE_COMMIT.md

@@ -0,0 +1,232 @@
+# Before-Commit Checklist
+
+This checklist defines validation rules and quality standards that must be met before committing changes to this project.
+
+## Quick Check
+
+Run before every commit:
+
+```bash
+# Run tests
+npm test
+
+# Check for linting errors
+npm run lint
+
+# Build the project
+npm run build
+```
+
+---
+
+## 1. Code Quality
+
+### 1.1 Tests
+- [ ] All existing tests pass
+- [ ] New code has appropriate tests
+- [ ] Test coverage meets project threshold
+- [ ] No skipped tests without documented reason
+
+### 1.2 Linting & Formatting
+- [ ] No linting errors (`npm run lint`)
+- [ ] Code follows project style guide
+- [ ] Consistent formatting applied
+- [ ] No unused imports or variables
+
+### 1.3 Type Safety (if applicable)
+- [ ] No TypeScript errors (`tsc --noEmit`)
+- [ ] Proper types for function parameters and returns
+- [ ] No `any` types without justification
+- [ ] Interface definitions for complex objects
+
+### 1.4 Build
+- [ ] Project builds successfully (`npm run build`)
+- [ ] No build warnings (or documented exceptions)
+- [ ] Bundle size within acceptable limits
+
+---
+
+## 2. Git Standards
+
+### 2.1 Conventional Commits
+Use the format: `type(scope): description`
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `style` | Formatting, no code change |
+| `refactor` | Code restructuring |
+| `perf` | Performance improvement |
+| `test` | Adding tests |
+| `chore` | Maintenance tasks |
+| `ci` | CI/CD changes |
+| `revert` | Revert previous commit |
+
+**Examples:**
+```
+feat(auth): add social login support
+fix(api): handle null response from server
+docs(readme): update installation instructions
+refactor(utils): simplify date formatting logic
+```
+
+### 2.2 Commit Message Guidelines
+- [ ] First line under 72 characters
+- [ ] Use imperative mood ("add" not "added")
+- [ ] Reference issues when applicable (`#123`)
+- [ ] Separate subject from body with blank line
+- [ ] Explain "what" and "why" (not "how")
+
+### 2.3 Branch Hygiene
+- [ ] Working on correct branch
+- [ ] Branch is up-to-date with main/master
+- [ ] No merge conflicts
+- [ ] Feature branch naming: `feature/description`
+- [ ] Fix branch naming: `fix/description`
+
+---
+
+## 3. Security
+
+### 3.1 Credentials & Secrets
+- [ ] No API keys in code
+- [ ] No passwords in code
+- [ ] No tokens in code
+- [ ] `.env` files not committed
+- [ ] Secrets in environment variables only
+
+### 3.2 Dependencies
+- [ ] No known vulnerabilities (`npm audit`)
+- [ ] Dependencies from trusted sources
+- [ ] Lock file (`package-lock.json`) updated
+- [ ] No unnecessary dependencies added
+
+### 3.3 Input Validation
+- [ ] User inputs sanitized
+- [ ] SQL injection prevented
+- [ ] XSS vulnerabilities addressed
+- [ ] CSRF protection in place (if applicable)
+
+---
+
+## 4. Documentation
+
+### 4.1 Code Documentation
+- [ ] Complex logic has comments
+- [ ] Public APIs have JSDoc/docstrings
+- [ ] README updated for new features
+- [ ] Breaking changes documented
+
+### 4.2 Changelog
+- [ ] CHANGELOG.md updated for user-facing changes
+- [ ] Version number updated if releasing
+- [ ] Migration guide for breaking changes
+
+### 4.3 API Documentation
+- [ ] New endpoints documented
+- [ ] Request/response examples provided
+- [ ] Error responses documented
+
+---
+
+## 5. Performance
+
+### 5.1 Code Efficiency
+- [ ] No obvious performance regressions
+- [ ] Database queries optimized
+- [ ] No N+1 query problems
+- [ ] Appropriate caching in place
+
+### 5.2 Assets
+- [ ] Images optimized
+- [ ] Large files not committed (use LFS if needed)
+- [ ] Bundle size checked
+- [ ] Lazy loading where appropriate
+
+---
+
+## 6. Review Checklist
+
+### 6.1 Self-Review
+- [ ] Code reviewed by yourself
+- [ ] Changes match requirements
+- [ ] Edge cases handled
+- [ ] Error handling in place
+- [ ] Logging appropriate (not excessive)
+
+### 6.2 Code Smell Check
+- [ ] No duplicate code
+- [ ] Functions are single-purpose
+- [ ] Naming is clear and consistent
+- [ ] No magic numbers/strings
+- [ ] Appropriate abstraction level
+
+### 6.3 Testing Mindset
+- [ ] "What could go wrong?" considered
+- [ ] Boundary conditions tested
+- [ ] Error paths tested
+- [ ] Happy path works
+
+---
+
+## 7. Environment-Specific
+
+### 7.1 Development
+- [ ] Works in development environment
+- [ ] Dev dependencies separate from prod
+
+### 7.2 Production Readiness
+- [ ] Feature flags for incomplete features
+- [ ] Backwards compatibility maintained
+- [ ] Rollback plan exists
+- [ ] Monitoring in place for new features
+
+---
+
+## Quick Reference Commands
+
+```bash
+# Run all checks
+npm test && npm run lint && npm run build
+
+# Check for security issues
+npm audit
+
+# Format code
+npm run format
+
+# Type check (TypeScript)
+npx tsc --noEmit
+
+# Git status
+git status
+
+# Stage changes
+git add -A
+
+# Commit with conventional format
+git commit -m "type(scope): description"
+```
+
+---
+
+## AI-Assisted Development
+
+When using OMGKIT AI agents:
+
+1. **Review AI-generated code** before committing
+2. **Run tests** after AI modifications
+3. **Check for sensitive data** in AI outputs
+4. **Validate logic** - AI can make mistakes
+
+---
+
+## Customization
+
+Add project-specific rules below this line:
+
+---
+
+<!-- PROJECT-SPECIFIC RULES -->