codehava-agent-kit 1.0.0 → 2.0.0

package/templates/.agent/skills/git-hooks-automation/SKILL.md

@@ -0,0 +1,416 @@
+---
+name: git-hooks-automation
+description: "Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI."
+risk: safe
+source: community
+date_added: "2026-03-07"
+---
+
+# Git Hooks Automation
+
+Automate code quality enforcement at the Git level. Set up hooks that lint, format, test, and validate before commits and pushes ever reach your CI pipeline — catching issues in seconds instead of minutes.
+
+## When to Use This Skill
+
+- User asks to "set up git hooks" or "add pre-commit hooks"
+- Configuring Husky, lint-staged, or the pre-commit framework
+- Enforcing commit message conventions (Conventional Commits, commitlint)
+- Automating linting, formatting, or type-checking before commits
+- Setting up pre-push hooks for test runners
+- Migrating from Husky v4 to v9+ or adopting hooks from scratch
+- User mentions "pre-commit", "commit-msg", "pre-push", "lint-staged", or "githooks"
+
+## Git Hooks Fundamentals
+
+Git hooks are scripts that run automatically at specific points in the Git workflow. They live in `.git/hooks/` and are not version-controlled by default — which is why tools like Husky exist.
+
+### Hook Types & When They Fire
+
+| Hook | Fires When | Common Use |
+|---|---|---|
+| `pre-commit` | Before commit is created | Lint, format, type-check staged files |
+| `prepare-commit-msg` | After default msg, before editor | Auto-populate commit templates |
+| `commit-msg` | After user writes commit message | Enforce commit message format |
+| `post-commit` | After commit is created | Notifications, logging |
+| `pre-push` | Before push to remote | Run tests, check branch policies |
+| `pre-rebase` | Before rebase starts | Prevent rebase on protected branches |
+| `post-merge` | After merge completes | Install deps, run migrations |
+| `post-checkout` | After checkout/switch | Install deps, rebuild assets |
+
+### Native Git Hooks (No Framework)
+
+```bash
+# Create a pre-commit hook manually
+cat > .git/hooks/pre-commit << 'EOF'
+#!/bin/sh
+set -e
+
+# Run linter on staged files only
+STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep -E '\.(js|ts|jsx|tsx)$' || true)
+
+if [ -n "$STAGED_FILES" ]; then
+  echo "🔍 Linting staged files..."
+  echo "$STAGED_FILES" | xargs npx eslint --fix
+  echo "$STAGED_FILES" | xargs git add  # Re-stage after fixes
+fi
+EOF
+chmod +x .git/hooks/pre-commit
+```
+
+**Problem**: `.git/hooks/` is local-only and not shared with the team. Use a framework instead.
+
+## Husky + lint-staged (Node.js Projects)
+
+The modern standard for JavaScript/TypeScript projects. Husky manages Git hooks; lint-staged runs commands only on staged files for speed.
+
+### Quick Setup (Husky v9+)
+
+```bash
+# Install
+npm install --save-dev husky lint-staged
+
+# Initialize Husky (creates .husky/ directory)
+npx husky init
+
+# The init command creates a pre-commit hook — edit it:
+echo "npx lint-staged" > .husky/pre-commit
+```
+
+### Configure lint-staged in `package.json`
+
+```json
+{
+  "lint-staged": {
+    "*.{js,jsx,ts,tsx}": [
+      "eslint --fix --max-warnings=0",
+      "prettier --write"
+    ],
+    "*.{css,scss}": [
+      "prettier --write",
+      "stylelint --fix"
+    ],
+    "*.{json,md,yml,yaml}": [
+      "prettier --write"
+    ]
+  }
+}
+```
+
+### Add Commit Message Linting
+
+```bash
+# Install commitlint
+npm install --save-dev @commitlint/cli @commitlint/config-conventional
+
+# Create commitlint config
+cat > commitlint.config.js << 'EOF'
+module.exports = {
+  extends: ['@commitlint/config-conventional'],
+  rules: {
+    'type-enum': [2, 'always', [
+      'feat', 'fix', 'docs', 'style', 'refactor',
+      'perf', 'test', 'build', 'ci', 'chore', 'revert'
+    ]],
+    'subject-max-length': [2, 'always', 72],
+    'body-max-line-length': [2, 'always', 100]
+  }
+};
+EOF
+
+# Add commit-msg hook
+echo "npx --no -- commitlint --edit \$1" > .husky/commit-msg
+```
+
+### Add Pre-Push Hook
+
+```bash
+# Run tests before pushing
+echo "npm test" > .husky/pre-push
+```
+
+### Complete Husky Directory Structure
+
+```
+project/
+├── .husky/
+│   ├── pre-commit        # npx lint-staged
+│   ├── commit-msg        # npx --no -- commitlint --edit $1
+│   └── pre-push          # npm test
+├── commitlint.config.js
+├── package.json          # lint-staged config here
+└── ...
+```
+
+## pre-commit Framework (Python / Polyglot)
+
+Language-agnostic framework that works with any project. Hooks are defined in YAML and run in isolated environments.
+
+### Setup
+
+```bash
+# Install (Python required)
+pip install pre-commit
+
+# Create config
+cat > .pre-commit-config.yaml << 'EOF'
+repos:
+  # Built-in checks
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-json
+      - id: check-added-large-files
+        args: ['--maxkb=500']
+      - id: check-merge-conflict
+      - id: detect-private-key
+
+  # Python formatting
+  - repo: https://github.com/psf/black
+    rev: 24.4.2
+    hooks:
+      - id: black
+
+  # Python linting
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.4.4
+    hooks:
+      - id: ruff
+        args: ['--fix']
+      - id: ruff-format
+
+  # Shell script linting
+  - repo: https://github.com/shellcheck-py/shellcheck-py
+    rev: v0.10.0.1
+    hooks:
+      - id: shellcheck
+
+  # Commit message format
+  - repo: https://github.com/compilerla/conventional-pre-commit
+    rev: v3.2.0
+    hooks:
+      - id: conventional-pre-commit
+        stages: [commit-msg]
+EOF
+
+# Install hooks into .git/hooks/
+pre-commit install
+pre-commit install --hook-type commit-msg
+
+# Run against all files (first time)
+pre-commit run --all-files
+```
+
+### Key Commands
+
+```bash
+pre-commit install              # Install hooks
+pre-commit run --all-files      # Run on everything (CI or first setup)
+pre-commit autoupdate           # Update hook versions
+pre-commit run <hook-id>        # Run a specific hook
+pre-commit clean                # Clear cached environments
+```
+
+## Custom Hook Scripts (Any Language)
+
+For projects not using Node or Python, write hooks directly in shell.
+
+### Portable Pre-Commit Hook
+
+```bash
+#!/bin/sh
+# .githooks/pre-commit — Team-shared hooks directory
+set -e
+
+echo "=== Pre-Commit Checks ==="
+
+# 1. Prevent commits to main/master
+BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null || echo "detached")
+if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
+  echo "❌ Direct commits to $BRANCH are not allowed. Use a feature branch."
+  exit 1
+fi
+
+# 2. Check for debugging artifacts
+if git diff --cached --diff-filter=ACM | grep -nE '(console\.log|debugger|binding\.pry|import pdb)' > /dev/null 2>&1; then
+  echo "⚠️  Debug statements found in staged files:"
+  git diff --cached --diff-filter=ACM | grep -nE '(console\.log|debugger|binding\.pry|import pdb)'
+  echo "Remove them or use git commit --no-verify to bypass."
+  exit 1
+fi
+
+# 3. Check for large files (>1MB)
+LARGE_FILES=$(git diff --cached --name-only --diff-filter=ACM | while read f; do
+  size=$(wc -c < "$f" 2>/dev/null || echo 0)
+  if [ "$size" -gt 1048576 ]; then echo "$f ($((size/1024))KB)"; fi
+done)
+if [ -n "$LARGE_FILES" ]; then
+  echo "❌ Large files detected:"
+  echo "$LARGE_FILES"
+  exit 1
+fi
+
+# 4. Check for secrets patterns
+if git diff --cached --diff-filter=ACM | grep -nEi '(AKIA[0-9A-Z]{16}|sk-[a-zA-Z0-9]{48}|ghp_[a-zA-Z0-9]{36}|password\s*=\s*["\x27][^"\x27]+["\x27])' > /dev/null 2>&1; then
+  echo "🚨 Potential secrets detected in staged changes! Review before committing."
+  exit 1
+fi
+
+echo "✅ All pre-commit checks passed"
+```
+
+### Share Custom Hooks via `core.hooksPath`
+
+```bash
+# In your repo, set a shared hooks directory
+git config core.hooksPath .githooks
+
+# Add to project setup docs or Makefile
+# Makefile
+setup:
+	git config core.hooksPath .githooks
+	chmod +x .githooks/*
+```
+
+## CI Integration
+
+Hooks are a first line of defense, but CI is the source of truth.
+
+### Run pre-commit in CI (GitHub Actions)
+
+```yaml
+# .github/workflows/lint.yml
+name: Lint
+on: [push, pull_request]
+jobs:
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - uses: pre-commit/action@v3.0.1
+```
+
+### Run lint-staged in CI (Validation Only)
+
+```yaml
+# Validate that lint-staged would pass (catch bypassed hooks)
+name: Lint Check
+on: [pull_request]
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - run: npm ci
+      - run: npx eslint . --max-warnings=0
+      - run: npx prettier --check .
+```
+
+## Common Pitfalls & Fixes
+
+### Hooks Not Running
+
+| Symptom | Cause | Fix |
+|---|---|---|
+| Hooks silently skipped | Not installed in `.git/hooks/` | Run `npx husky init` or `pre-commit install` |
+| "Permission denied" | Hook file not executable | `chmod +x .husky/pre-commit` |
+| Hooks run but wrong ones | Stale hooks from old setup | Delete `.git/hooks/` contents, reinstall |
+| Works locally, fails in CI | Different Node/Python versions | Pin versions in CI config |
+
+### Performance Issues
+
+```json
+// ❌ Slow: runs on ALL files every commit
+{
+  "scripts": {
+    "precommit": "eslint src/ && prettier --write src/"
+  }
+}
+
+// ✅ Fast: lint-staged runs ONLY on staged files
+{
+  "lint-staged": {
+    "*.{js,ts}": ["eslint --fix", "prettier --write"]
+  }
+}
+```
+
+### Bypassing Hooks (When Needed)
+
+```bash
+# Skip all hooks for a single commit
+git commit --no-verify -m "wip: quick save"
+
+# Skip pre-push only
+git push --no-verify
+
+# Skip specific pre-commit hooks
+SKIP=eslint git commit -m "fix: update config"
+```
+
+> **Warning**: Bypassing hooks should be rare. If your team frequently bypasses, the hooks are too slow or too strict — fix them.
+
+## Migration Guide
+
+### Husky v4 → v9 Migration
+
+```bash
+# 1. Remove old Husky
+npm uninstall husky
+rm -rf .husky
+
+# 2. Remove old config from package.json
+# Delete "husky": { "hooks": { ... } } section
+
+# 3. Install fresh
+npm install --save-dev husky
+npx husky init
+
+# 4. Recreate hooks
+echo "npx lint-staged" > .husky/pre-commit
+echo "npx --no -- commitlint --edit \$1" > .husky/commit-msg
+
+# 5. Clean up — old Husky used package.json config,
+#    new Husky uses .husky/ directory with plain scripts
+```
+
+### Adopting Hooks on an Existing Project
+
+```bash
+# Step 1: Start with formatting only (low friction)
+# lint-staged config:
+{ "*.{js,ts}": ["prettier --write"] }
+
+# Step 2: Add linting after team adjusts (1-2 weeks later)
+{ "*.{js,ts}": ["eslint --fix", "prettier --write"] }
+
+# Step 3: Add commit message linting
+# Step 4: Add pre-push test runner
+
+# Gradual adoption prevents team resistance
+```
+
+## Key Principles
+
+- **Staged files only** — Never lint the entire codebase on every commit
+- **Auto-fix when possible** — `--fix` flags reduce developer friction
+- **Fast hooks** — Pre-commit should complete in < 5 seconds
+- **Fail loud** — Clear error messages with actionable fixes
+- **Team-shared** — Use Husky or `core.hooksPath` so hooks are version-controlled
+- **CI as backup** — Hooks are convenience; CI is the enforcer
+- **Gradual adoption** — Start with formatting, add linting, then testing
+
+## Related Skills
+
+- `@codebase-audit-pre-push` - Deep audit before GitHub push
+- `@verification-before-completion` - Verification before claiming work is done
+- `@bash-pro` - Advanced shell scripting for custom hooks
+- `@github-actions-templates` - CI/CD workflow templates

package/templates/.agent/skills/git-pr-workflows-git-workflow/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: git-pr-workflows-git-workflow
+description: "Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g"
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+
+# Complete Git Workflow with Multi-Agent Orchestration
+
+Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.
+
+[Extended thinking: This workflow coordinates multiple specialized agents to ensure code quality before commits are made. The code-reviewer agent performs initial quality checks, test-automator ensures all tests pass, and deployment-engineer verifies production readiness. By orchestrating these agents sequentially with context passing, we prevent broken code from entering the repository while maintaining high velocity. The workflow supports both trunk-based and feature-branch strategies with configurable options for different team needs.]
+
+## Use this skill when
+
+- Working on complete git workflow with multi-agent orchestration tasks or workflows
+- Needing guidance, best practices, or checklists for complete git workflow with multi-agent orchestration
+
+## Do not use this skill when
+
+- The task is unrelated to complete git workflow with multi-agent orchestration
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Configuration
+
+**Target branch**: $ARGUMENTS (defaults to 'main' if not specified)
+
+**Supported flags**:
+- `--skip-tests`: Skip automated test execution (use with caution)
+- `--draft-pr`: Create PR as draft for work-in-progress
+- `--no-push`: Perform all checks but don't push to remote
+- `--squash`: Squash commits before pushing
+- `--conventional`: Enforce Conventional Commits format strictly
+- `--trunk-based`: Use trunk-based development workflow
+- `--feature-branch`: Use feature branch workflow (default)
+
+## Phase 1: Pre-Commit Review and Analysis
+
+### 1. Code Quality Assessment
+- Use Task tool with subagent_type="code-reviewer"
+- Prompt: "Review all uncommitted changes for code quality issues. Check for: 1) Code style violations, 2) Security vulnerabilities, 3) Performance concerns, 4) Missing error handling, 5) Incomplete implementations. Generate a detailed report with severity levels (critical/high/medium/low) and provide specific line-by-line feedback. Output format: JSON with {issues: [], summary: {critical: 0, high: 0, medium: 0, low: 0}, recommendations: []}"
+- Expected output: Structured code review report for next phase
+
+### 2. Dependency and Breaking Change Analysis
+- Use Task tool with subagent_type="code-reviewer"
+- Prompt: "Analyze the changes for: 1) New dependencies or version changes, 2) Breaking API changes, 3) Database schema modifications, 4) Configuration changes, 5) Backward compatibility issues. Context from previous review: [insert issues summary]. Identify any changes that require migration scripts or documentation updates."
+- Context from previous: Code quality issues that might indicate breaking changes
+- Expected output: Breaking change assessment and migration requirements
+
+## Phase 2: Testing and Validation
+
+### 1. Test Execution and Coverage
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Execute all test suites for the modified code. Run: 1) Unit tests, 2) Integration tests, 3) End-to-end tests if applicable. Generate coverage report and identify any untested code paths. Based on review issues: [insert critical/high issues], ensure tests cover the problem areas. Provide test results in format: {passed: [], failed: [], skipped: [], coverage: {statements: %, branches: %, functions: %, lines: %}, untested_critical_paths: []}"
+- Context from previous: Critical code review issues that need test coverage
+- Expected output: Complete test results and coverage metrics
+
+### 2. Test Recommendations and Gap Analysis
+- Use Task tool with subagent_type="unit-testing::test-automator"
+- Prompt: "Based on test results [insert summary] and code changes, identify: 1) Missing test scenarios, 2) Edge cases not covered, 3) Integration points needing verification, 4) Performance benchmarks needed. Generate test implementation recommendations prioritized by risk. Consider the breaking changes identified: [insert breaking changes]."
+- Context from previous: Test results, breaking changes, untested paths
+- Expected output: Prioritized list of additional tests needed
+
+## Phase 3: Commit Message Generation
+
+### 1. Change Analysis and Categorization
+- Use Task tool with subagent_type="code-reviewer"
+- Prompt: "Analyze all changes and categorize them according to Conventional Commits specification. Identify the primary change type (feat/fix/docs/style/refactor/perf/test/build/ci/chore/revert) and scope. For changes: [insert file list and summary], determine if this should be a single commit or multiple atomic commits. Consider test results: [insert test summary]."
+- Context from previous: Test results, code review summary
+- Expected output: Commit structure recommendation
+
+### 2. Conventional Commit Message Creation
+- Use Task tool with subagent_type="llm-application-dev::prompt-engineer"
+- Prompt: "Create Conventional Commits format message(s) based on categorization: [insert categorization]. Format: <type>(<scope>): <subject> with blank line then <body> explaining what and why (not how), then <footer> with BREAKING CHANGE: if applicable. Include: 1) Clear subject line (50 chars max), 2) Detailed body explaining rationale, 3) References to issues/tickets, 4) Co-authors if applicable. Consider the impact: [insert breaking changes if any]."
+- Context from previous: Change categorization, breaking changes
+- Expected output: Properly formatted commit message(s)
+
+## Phase 4: Branch Strategy and Push Preparation
+
+### 1. Branch Management
+- Use Task tool with subagent_type="cicd-automation::deployment-engineer"
+- Prompt: "Based on workflow type [--trunk-based or --feature-branch], prepare branch strategy. For feature branch: ensure branch name follows pattern (feature|bugfix|hotfix)/<ticket>-<description>. For trunk-based: prepare for direct main push with feature flag strategy if needed. Current branch: [insert branch], target: [insert target branch]. Verify no conflicts with target branch."
+- Expected output: Branch preparation commands and conflict status
+
+### 2. Pre-Push Validation
+- Use Task tool with subagent_type="cicd-automation::deployment-engineer"
+- Prompt: "Perform final pre-push checks: 1) Verify all CI checks will pass, 2) Confirm no sensitive data in commits, 3) Validate commit signatures if required, 4) Check branch protection rules, 5) Ensure all review comments addressed. Test summary: [insert test results]. Review status: [insert review summary]."
+- Context from previous: All previous validation results
+- Expected output: Push readiness confirmation or blocking issues
+
+## Phase 5: Pull Request Creation
+
+### 1. PR Description Generation
+- Use Task tool with subagent_type="documentation-generation::docs-architect"
+- Prompt: "Create comprehensive PR description including: 1) Summary of changes (what and why), 2) Type of change checklist, 3) Testing performed summary from [insert test results], 4) Screenshots/recordings if UI changes, 5) Deployment notes from [insert deployment considerations], 6) Related issues/tickets, 7) Breaking changes section if applicable: [insert breaking changes], 8) Reviewer checklist. Format as GitHub-flavored Markdown."
+- Context from previous: All validation results, test outcomes, breaking changes
+- Expected output: Complete PR description in Markdown
+
+### 2. PR Metadata and Automation Setup
+- Use Task tool with subagent_type="cicd-automation::deployment-engineer"
+- Prompt: "Configure PR metadata: 1) Assign appropriate reviewers based on CODEOWNERS, 2) Add labels (type, priority, component), 3) Link related issues, 4) Set milestone if applicable, 5) Configure merge strategy (squash/merge/rebase), 6) Set up auto-merge if all checks pass. Consider draft status: [--draft-pr flag]. Include test status: [insert test summary]."
+- Context from previous: PR description, test results, review status
+- Expected output: PR configuration commands and automation rules
+
+## Success Criteria
+
+- ✅ All critical and high-severity code issues resolved
+- ✅ Test coverage maintained or improved (target: >80%)
+- ✅ All tests passing (unit, integration, e2e)
+- ✅ Commit messages follow Conventional Commits format
+- ✅ No merge conflicts with target branch
+- ✅ PR description complete with all required sections
+- ✅ Branch protection rules satisfied
+- ✅ Security scanning completed with no critical vulnerabilities
+- ✅ Performance benchmarks within acceptable thresholds
+- ✅ Documentation updated for any API changes
+
+## Rollback Procedures
+
+In case of issues after merge:
+
+1. **Immediate Revert**: Create revert PR with `git revert <commit-hash>`
+2. **Feature Flag Disable**: If using feature flags, disable immediately
+3. **Hotfix Branch**: For critical issues, create hotfix branch from main
+4. **Communication**: Notify team via designated channels
+5. **Root Cause Analysis**: Document issue in postmortem template
+
+## Best Practices Reference
+
+- **Commit Frequency**: Commit early and often, but ensure each commit is atomic
+- **Branch Naming**: `(feature|bugfix|hotfix|docs|chore)/<ticket-id>-<brief-description>`
+- **PR Size**: Keep PRs under 400 lines for effective review
+- **Review Response**: Address review comments within 24 hours
+- **Merge Strategy**: Squash for feature branches, merge for release branches
+- **Sign-Off**: Require at least 2 approvals for main branch changes