omgkit 2.17.0 → 2.19.0

package/README.md

@@ -424,6 +424,38 @@ omgkit uninstall    # Remove plugin
 omgkit help         # Show help
 ```
 
+## ✅ Before-Commit Validation
+
+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 4800+ validation tests
+```
+
+| 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 |
+
+### 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
 
 After `omgkit init`:
@@ -441,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.17.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/agents/brainstormer.md

@@ -1,6 +1,6 @@
 ---
 name: brainstormer
-description: Creative exploration, ideation, option generation. Use for brainstorming.
+description: Creative exploration agent specialized for ideation, brainstorming sessions, and systematic option generation for complex problems.
 tools: Read, WebSearch, Glob
 model: inherit
 skills:

package/plugin/agents/project-manager.md

@@ -44,3 +44,34 @@ You coordinate and track progress.
 - Track dependencies
 - Manage blockers
 - Report progress
+
+## Project Tracking Process
+
+### Daily Standup Template
+```markdown
+## Daily Update: [Date]
+
+### Yesterday
+- Completed: [List completed tasks]
+- Agents involved: [Names]
+
+### Today
+- Planned: [List planned tasks]
+- Assigned to: [Agent names]
+
+### Blockers
+- [Issue]: [Proposed resolution]
+```
+
+### Sprint Planning
+1. Review backlog
+2. Estimate complexity
+3. Assign to agents
+4. Set success criteria
+5. Track progress daily
+
+## Decision Log
+Track key decisions with:
+- Context and options
+- Decision rationale
+- Owner and date

package/plugin/commands/git/cm.md

@@ -7,7 +7,11 @@ allowed-tools: Bash
 
 Quick conventional commit for staged changes.
 
+## Usage
+
 ```bash
 git add -A
 git commit -m "type(scope): message"
 ```
+
+Follow conventional commit format: `feat`, `fix`, `docs`, `chore`, `refactor`, `test`.

package/plugin/commands/sprint/sprint-new.md

@@ -1,7 +1,7 @@
 ---
 description: Create new sprint
 allowed-tools: Task, Read, Write, Grep, Glob
-argument-hint: [name] [--propose]
+argument-hint: "[name] [--propose]"
 ---
 
 # 🏃 Sprint New: $ARGUMENTS

package/plugin/registry.yaml

@@ -1,15 +1,15 @@
 # OMGKIT Component Registry
 # Single Source of Truth for Agents, Skills, Commands, Workflows, and MCPs
-# Version: 2.17.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/plugin/stdrules/omgkit/OMGKIT_BEFORE_COMMIT_RULES.md

@@ -0,0 +1,367 @@
+# OMGKIT Before-Commit Rules v1.0
+
+> Comprehensive quality gates that MUST pass before any commit to OMGKIT.
+> Run `npm test` to validate all rules automatically.
+
+---
+
+## Overview
+
+This document defines the mandatory validation checks that must pass before committing changes to OMGKIT. These rules ensure system integrity, documentation quality, and proper command registration.
+
+---
+
+## 1. Test Validation (MANDATORY)
+
+All commits MUST pass the complete test suite:
+
+```bash
+npm test
+```
+
+**Minimum Requirements:**
+- All tests must pass (0 failures)
+- Current baseline: 3700+ tests
+- Coverage must not decrease
+
+---
+
+## 2. Registry Integrity
+
+### 2.1 Registry Sync
+
+The `registry.yaml` file must be synchronized with actual component files:
+
+| Check | Description |
+|-------|-------------|
+| Agent Sync | All registered agents exist as `.md` files in `plugin/agents/` |
+| Workflow Sync | All registered workflows exist as `.md` files in `plugin/workflows/` |
+| Namespace Sync | All command namespaces in registry exist as directories |
+| Category Sync | All skill categories in registry exist as directories |
+
+**Validation Command:**
+```bash
+npm test -- tests/validation/registry-sync.test.js
+```
+
+### 2.2 Dependency Graph Integrity
+
+All component references must be valid:
+
+| Reference Type | Format | Example |
+|----------------|--------|---------|
+| Skill | `category/skill-name` | `methodology/writing-plans` |
+| Command | `/namespace:command-name` | `/dev:feature` |
+| Agent | `kebab-case` | `fullstack-developer` |
+| Workflow | `category/workflow-name` | `development/feature` |
+
+**Validation Command:**
+```bash
+npm test -- tests/validation/dependency-graph.test.js
+```
+
+---
+
+## 3. Command Registration (CRITICAL)
+
+### 3.1 Slash Command Requirements
+
+Every command in OMGKIT MUST be registered as a Claude Code slash command. This means:
+
+**File Location:**
+- Commands must be in `plugin/commands/<namespace>/<command-name>.md`
+- Namespace directory must exist
+
+**Format Requirements:**
+- Command ID format: `/namespace:command-name`
+- All lowercase, hyphens for word separation
+- Namespace must be registered in `registry.yaml` under `command_namespaces`
+
+**Frontmatter Requirements:**
+```yaml
+---
+description: Clear description of what the command does
+argument-hint: <optional argument format>
+allowed-tools: List, Of, Allowed, Tools
+---
+```
+
+### 3.2 Command Registration Checklist
+
+| Requirement | Description |
+|-------------|-------------|
+| **File exists** | `plugin/commands/<namespace>/<name>.md` exists |
+| **Namespace registered** | Namespace in `registry.yaml` `command_namespaces` |
+| **Valid frontmatter** | Has `description` field |
+| **Content present** | Body has usage instructions |
+| **Format compliance** | Follows `/namespace:command-name` format |
+
+### 3.3 Current Command Namespaces
+
+All commands must belong to one of these registered namespaces:
+
+| Namespace | Purpose |
+|-----------|---------|
+| `dev` | Development commands (feature, fix, test, tdd, review) |
+| `planning` | Planning commands (plan, brainstorm, research, doc) |
+| `git` | Git operations (commit, ship, pr, deploy) |
+| `quality` | Quality commands (security-scan, refactor, optimize) |
+| `omega` | Omega thinking (10x, 100x, 1000x, principles) |
+| `sprint` | Sprint management (sprint-new, team-run, backlog) |
+| `workflow` | Workflow triggers (feature, bug-fix, rag-development) |
+| `auto` | Autonomous mode (init, start, approve, reject) |
+| `context` | Context management (mode, index, load, checkpoint) |
+| `design` | UI/UX design (screenshot, enhance, cro) |
+| `alignment` | System alignment (health, deps) |
+| `security` | Security commands (scan, audit) |
+| `data` | Data commands (pipeline, quality) |
+| `ml` | ML commands (train, evaluate) |
+| `game` | Game dev commands (balance, optimize) |
+| `iot` | IoT commands (provision) |
+| `perf` | Performance commands (profile, benchmark) |
+| `domain` | Domain modeling (analyze, map) |
+| `platform` | Platform engineering (blueprint) |
+| `sre` | SRE commands (dashboard) |
+
+---
+
+## 4. Documentation Quality Standards
+
+### 4.1 Agent Documentation
+
+**Minimum Requirements:**
+
+| Field | Requirement |
+|-------|-------------|
+| File location | `plugin/agents/<agent-name>.md` |
+| Frontmatter | `skills` and `commands` arrays |
+| Description | 50-200 words explaining purpose |
+| Responsibilities | 3-5 primary, 2-4 secondary |
+| Minimum lines | 50+ lines of content |
+
+**Required Sections:**
+- Description/Overview
+- Primary Responsibilities
+- Skills Used
+- Commands Triggered
+- Usage Examples
+
+### 4.2 Command Documentation
+
+**Minimum Requirements:**
+
+| Field | Requirement |
+|-------|-------------|
+| File location | `plugin/commands/<namespace>/<name>.md` |
+| Frontmatter | `description`, `allowed-tools` |
+| Description | Clear, actionable description |
+| Minimum lines | 15+ lines of content |
+
+**Required Frontmatter Fields:**
+```yaml
+---
+description: What the command does (required)
+argument-hint: Expected arguments (recommended)
+allowed-tools: Comma-separated tool list (required)
+---
+```
+
+### 4.3 Skill Documentation
+
+**Minimum Requirements:**
+
+| Field | Requirement |
+|-------|-------------|
+| File location | `plugin/skills/<category>/<name>/SKILL.md` |
+| Frontmatter | `name`, `description` |
+| Description | Third-person, 50-150 words |
+| Minimum lines | 30+ lines of content |
+
+**Must Follow:** `plugin/stdrules/SKILL_STANDARDS.md`
+
+### 4.4 Workflow Documentation
+
+**Minimum Requirements:**
+
+| Field | Requirement |
+|-------|-------------|
+| File location | `plugin/workflows/<category>/<name>.md` |
+| Frontmatter | name, description, category, complexity, agents, skills, commands |
+| Steps | Clear step-by-step process |
+| Quality Gates | Completion checklist |
+| Minimum lines | 50+ lines of content |
+
+**Required Frontmatter Fields:**
+```yaml
+---
+name: workflow-name
+description: What the workflow accomplishes
+category: workflow-category
+complexity: low|medium|high|very-high
+estimated-time: Time estimate
+agents:
+  - agent-name
+skills:
+  - category/skill-name
+commands:
+  - /namespace:command-name
+prerequisites:
+  - Prerequisite 1
+---
+```
+
+---
+
+## 5. Content Quality Rules
+
+### 5.1 Prohibited Content
+
+- No placeholder text: `TODO`, `FIXME`, `XXX`, `HACK`
+- No empty sections
+- No broken internal links
+- No duplicate content across components
+
+### 5.2 Required Content Elements
+
+**Code Blocks:**
+- Must have language specifier
+- Must be properly indented
+- Must be functional examples
+
+**Links:**
+- Internal links must be relative
+- External links must be valid
+- All referenced files must exist
+
+### 5.3 Formatting Standards
+
+- Use proper Markdown heading hierarchy (h1 > h2 > h3)
+- Use consistent list formatting
+- Use tables for structured data
+- Use code blocks for commands/examples
+
+---
+
+## 6. Cross-Reference Validation
+
+### 6.1 Forward References (dependsOn)
+
+All references in component frontmatter must point to existing components:
+
+| Source | Reference Type | Target |
+|--------|---------------|--------|
+| Agent | skills | Skill files |
+| Agent | commands | Command files |
+| Workflow | agents | Agent files |
+| Workflow | skills | Skill files |
+| Workflow | commands | Command files |
+
+### 6.2 Reverse References (usedBy)
+
+The dependency graph must correctly compute:
+
+| Component | usedBy |
+|-----------|--------|
+| Skill | Agents that use it, Workflows that include it |
+| Command | Agents that trigger it, Workflows that include it |
+| Agent | Workflows that orchestrate it |
+
+---
+
+## 7. Version Management
+
+### 7.1 Version Bump Requirements
+
+When releasing:
+- Bump `package.json` version
+- Bump `plugin/registry.yaml` version
+- Update version comment in registry header
+
+### 7.2 Changelog
+
+Document changes in commit message following conventional commits:
+- `feat:` New features
+- `fix:` Bug fixes
+- `docs:` Documentation changes
+- `chore:` Maintenance tasks
+- `refactor:` Code refactoring
+- `test:` Test additions/changes
+
+---
+
+## 8. Pre-Commit Checklist
+
+### Quick Validation
+
+```bash
+# Run all tests
+npm test
+
+# Check specific validations
+npm test -- tests/validation/registry-sync.test.js
+npm test -- tests/validation/dependency-graph.test.js
+npm test -- tests/validation/before-commit.test.js
+npm test -- tests/validation/doc-quality.test.js
+npm test -- tests/validation/command-registration.test.js
+```
+
+### Manual Checklist
+
+- [ ] All tests pass (`npm test`)
+- [ ] Registry.yaml synced with actual files
+- [ ] All commands registered as slash commands
+- [ ] All command namespaces in registry
+- [ ] Documentation meets quality standards
+- [ ] No broken internal links
+- [ ] Dependency graph valid
+- [ ] Version bumped (if releasing)
+- [ ] Docs regenerated (`npm run docs:generate`)
+
+---
+
+## 9. Automated Validation
+
+### Test Files
+
+| Test File | Purpose |
+|-----------|---------|
+| `registry-sync.test.js` | Registry matches actual files |
+| `dependency-graph.test.js` | Dependency references valid |
+| `before-commit.test.js` | All pre-commit rules |
+| `doc-quality.test.js` | Documentation quality |
+| `command-registration.test.js` | Command slash registration |
+| `format.test.js` | Format compliance |
+| `alignment.test.js` | Alignment principle |
+
+### Running Validation
+
+```bash
+# Full validation
+npm test
+
+# Quick validation (key tests only)
+npm test -- tests/validation/before-commit.test.js
+```
+
+---
+
+## 10. Enforcement
+
+### CI/CD Integration
+
+These rules are enforced in CI:
+- All tests must pass before merge
+- Documentation must be regenerated
+- Version must be bumped for releases
+
+### Local Development
+
+Before committing:
+1. Run `npm test`
+2. Fix any failures
+3. Re-run until all pass
+4. Commit with proper message
+
+---
+
+*Think Omega. Build Omega. Be Omega.*

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