@vodailoc/kilo-kit-mcp 1.1.0

package/skills/kilo-kit/references/output-formats.md

@@ -0,0 +1,204 @@
+# 📋 Output Formats
+
+> Standard output format definitions for Kilo-Kit workflows.
+
+---
+
+## Hard-Gate Scan Report
+
+```yaml
+hard_gate_report:
+  timestamp: "<ISO-8601>"
+  task: "<brief task description>"
+
+  system_scan:
+    disk_space:
+      status: "pass|fail"
+      detail: "<e.g., 45% used, 120GB free>"
+    memory:
+      status: "pass|fail"
+      detail: "<e.g., 8GB available of 16GB>"
+    runtime_versions:
+      status: "pass|fail"
+      detail:
+        node: "<version or N/A>"
+        python: "<version or N/A>"
+        dotnet: "<version or N/A>"
+
+  codebase_scan:
+    project_structure:
+      status: "pass|fail"
+      files_scanned: <count>
+      relevant_files: ["<file1>", "<file2>"]
+    recent_changes:
+      status: "pass|fail"
+      commits_reviewed: <count>
+      relevant_commits: ["<sha1>", "<sha2>"]
+    existing_tests:
+      status: "pass|fail"
+      test_files_found: <count>
+      relevant_tests: ["<test1>", "<test2>"]
+
+  context_validation:
+    intent_confirmed: true|false
+    scope_verified: true|false
+    dependencies_identified: ["<dep1>", "<dep2>"]
+
+  gate_result: "OPEN|BLOCKED"
+  blocked_reasons: ["<reason1>"]  # empty if OPEN
+```
+
+---
+
+## Iron Law Compliance Report
+
+```yaml
+iron_law_compliance:
+  task_id: "<task identifier>"
+  timestamp: "<ISO-8601>"
+
+  law_1_evidence:
+    compliant: true|false
+    citations: ["<file:line — description>"]
+
+  law_2_scan_before_speak:
+    compliant: true|false
+    hard_gate_completed: true|false
+
+  law_3_verify_before_claim:
+    compliant: true|false
+    verification_method: "<tests|build|manual>"
+    verification_result: "pass|fail"
+
+  law_4_minimal_blast_radius:
+    compliant: true|false
+    files_changed: <count>
+    lines_changed: <count>
+
+  law_5_preserve_what_works:
+    compliant: true|false
+    unrelated_changes: <count>
+
+  law_6_trace_every_decision:
+    compliant: true|false
+    decisions_logged: <count>
+
+  law_7_fail_loud:
+    compliant: true|false
+    errors_reported: <count>
+    errors_hidden: <count>
+
+  overall: "COMPLIANT|VIOLATION"
+  violations: ["<law_number — description>"]  # empty if COMPLIANT
+```
+
+---
+
+## Decision Audit Trail Entry
+
+```yaml
+decision_entry:
+  id: "DEC-<timestamp>-<short_hash>"
+  timestamp: "<ISO-8601>"
+  phase: "hard-gate|routing|execution|verification"
+
+  context:
+    user_request: "<original request summary>"
+    current_state: "<what has been done so far>"
+    token_budget_remaining: <count>
+
+  decision:
+    action: "<what was decided>"
+    reasoning: "<why this action was chosen>"
+    evidence:
+      - source: "<file:line or command>"
+        finding: "<what was observed>"
+
+  alternatives:
+    - option: "<alternative approach>"
+      rejected_because: "<reason>"
+
+  outcome:
+    result: "success|failure|pending"
+    detail: "<additional context>"
+```
+
+---
+
+## Skill Execution Summary
+
+```yaml
+skill_execution:
+  skill: "<skill name>"
+  version: "<skill version>"
+  timestamp: "<ISO-8601>"
+
+  input:
+    user_request: "<request>"
+    hard_gate_result: "OPEN"
+    token_mode: "economy|standard|premium|critical"
+
+  execution:
+    phases_completed: ["<phase1>", "<phase2>"]
+    behaviors_used: ["<behavior1>", "<behavior2>"]
+    quality_gates:
+      pre_execution: "pass|fail"
+      per_behavior: "pass|fail"
+      post_execution: "pass|fail"
+      pre_completion: "pass|fail"
+
+  output:
+    changes_made:
+      - file: "<path>"
+        description: "<what changed>"
+    tests_run: <count>
+    tests_passed: <count>
+    verification: "pass|fail"
+
+  metrics:
+    tokens_used: <count>
+    duration_seconds: <count>
+    iron_law_compliant: true|false
+```
+
+---
+
+## Change Proposal Format
+
+```markdown
+## Change Proposal: <title>
+
+**Task:** <link to issue or request description>
+**Date:** <ISO-8601>
+
+### Evidence
+
+| # | Source | Finding |
+|---|--------|---------|
+| 1 | `<file:line>` | <observation> |
+| 2 | `<command output>` | <observation> |
+
+### Proposed Changes
+
+| File | Change | Reason |
+|------|--------|--------|
+| `<path>` | <description> | <why> |
+
+### Verification Plan
+
+- [ ] Unit tests pass
+- [ ] Integration tests pass
+- [ ] Manual verification performed
+- [ ] No regressions introduced
+
+### Iron Law Compliance
+
+- [x] Evidence cited for all changes
+- [x] Hard-Gate scan completed
+- [ ] Verification performed
+- [x] Minimal blast radius confirmed
+```
+
+---
+
+*Output Formats v1.0.0 — Kilo-Kit*

package/skills/kilo-kit/references/patterns.md

@@ -0,0 +1,156 @@
+# 📐 Patterns Reference
+
+> Reusable patterns for evidence-based AI agent workflows in Kilo-Kit.
+
+---
+
+## Pattern 1: Pre-Flight System Scan
+
+**Context:** Before any task execution, verify system readiness.
+
+**Structure:**
+
+```yaml
+pre_flight:
+  steps:
+    - name: Check disk space
+      command: "df -h ."
+      fail_if: "usage > 90%"
+    - name: Check memory
+      command: "free -m"
+      fail_if: "available < 256MB"  # Minimum for running build tools + tests concurrently
+    - name: Check runtime versions
+      command: "node --version && python3 --version"
+      fail_if: "version below minimum"
+    - name: Check running services
+      command: "ps aux | grep -E '(node|python|dotnet)'"
+      purpose: "Identify conflicts"
+```
+
+**When to use:** At the start of every Hard-Gate check.
+
+---
+
+## Pattern 2: Codebase Context Gathering
+
+**Context:** Understand the project before making changes.
+
+**Structure:**
+
+```yaml
+codebase_scan:
+  steps:
+    - name: Project structure
+      command: "find . -maxdepth 2 -type f -not -path './.git/*' | head -60"
+    - name: Recent changes
+      command: "git log --oneline -10"
+    - name: Relevant files
+      action: "Search for files related to the task keywords"
+    - name: Existing tests
+      command: "find . -name '*.test.*' -o -name '*.spec.*' | head -20"
+    - name: Dependencies
+      action: "Read package.json, requirements.txt, or equivalent"
+```
+
+**When to use:** During the codebase scan phase of Hard-Gate.
+
+---
+
+## Pattern 3: Evidence-Backed Change Proposal
+
+**Context:** Every recommended change must have traceable evidence.
+
+**Structure:**
+
+```markdown
+## Change Proposal
+
+**File:** `<path/to/file>:<line_number>`
+**Current behavior:** <what the code does now>
+**Proposed change:** <what the code should do>
+
+**Evidence:**
+1. Source: `<file:line>` — <what was observed>
+2. Test gap: `<test file>` — <what is missing>
+3. Impact: <scope of affected components>
+
+**Verification plan:**
+- [ ] Unit test added/updated
+- [ ] Existing tests still pass
+- [ ] Manual verification performed
+```
+
+**When to use:** Before any code modification.
+
+---
+
+## Pattern 4: Decision Audit Entry
+
+**Context:** Every significant decision must be logged.
+
+**Structure:**
+
+```yaml
+decision:
+  id: "DEC-<timestamp>"
+  action: "<what was decided>"
+  evidence:
+    - "<file:line or command output that supports this>"
+  alternatives_considered:
+    - option: "<alternative approach>"
+      rejected_because: "<reason>"
+  iron_law_compliance:
+    - law_1_evidence: true
+    - law_2_scan_completed: true
+    - law_3_verification_planned: true
+```
+
+**When to use:** At every routing and execution decision point.
+
+---
+
+## Pattern 5: Minimal Change Verification
+
+**Context:** Confirm that changes are focused and minimal.
+
+**Structure:**
+
+```yaml
+change_verification:
+  files_modified: ["<list of files>"]
+  lines_changed: <count>
+  scope_check:
+    - question: "Is every changed file directly related to the task?"
+      answer: "yes|no — <explanation>"
+    - question: "Could any change be removed without breaking the fix?"
+      answer: "yes|no — <explanation>"
+    - question: "Are there unintended side effects?"
+      answer: "yes|no — <explanation>"
+```
+
+**When to use:** Before completing any task (Iron Law #4: Minimal Blast Radius).
+
+---
+
+## Pattern 6: Failure Recovery
+
+**Context:** When an execution step fails, recover systematically.
+
+**Structure:**
+
+```yaml
+recovery:
+  failed_step: "<which step failed>"
+  error_output: "<actual error message>"
+  diagnosis:
+    - hypothesis: "<what might have caused it>"
+      evidence: "<supporting data>"
+  recovery_action: "<what to do next>"
+  hard_gate_recheck: true  # Always re-run Hard-Gate after failures
+```
+
+**When to use:** Whenever a behavior or quality gate fails.
+
+---
+
+*Patterns Reference v1.0.0 — Kilo-Kit*

package/skills/kilo-kit/references/performance-benchmarks.md

@@ -0,0 +1,90 @@
+# 📊 Performance Benchmarks
+
+> Target benchmarks for Hard-Gate scans, skill execution, and quality gates in Kilo-Kit.
+
+---
+
+## Hard-Gate Scan Benchmarks
+
+| Scan Phase | Target Duration | Max Acceptable | Notes |
+|------------|-----------------|----------------|-------|
+| System scan (disk, memory, runtime) | < 5s | 15s | Parallel checks recommended |
+| Codebase scan (structure, files) | < 10s | 30s | Depends on project size |
+| Context validation (intent, scope) | < 3s | 10s | Reasoning step |
+| **Total Hard-Gate** | **< 18s** | **55s** | Sum of all phases |
+
+---
+
+## Token Budget Benchmarks
+
+| Operation | Typical Tokens | Max Tokens | Mode |
+|-----------|---------------|------------|------|
+| Hard-Gate scan report | 200–500 | 800 | Economy |
+| Iron Law compliance check | 100–300 | 500 | Economy |
+| Skill routing decision | 150–400 | 600 | Standard |
+| Evidence gathering | 500–1500 | 3000 | Standard |
+| Code modification + verification | 1000–3000 | 8000 | Premium |
+| Root cause analysis | 2000–4500 | 10000 | Premium |
+| Security audit | 1500–3500 | 8000 | Critical |
+
+---
+
+## Quality Gate Pass Rates
+
+> Target pass rates for well-configured projects.
+
+| Gate | Target Pass Rate | Warning Threshold | Action if Below |
+|------|------------------|-------------------|-----------------|
+| Pre-Execution (intent, budget) | > 95% | < 90% | Improve intent parsing |
+| Per-Behavior (input/output validation) | > 90% | < 80% | Review behavior configs |
+| Post-Execution (tests, build) | > 85% | < 75% | Review test coverage |
+| Pre-Completion (verification) | > 98% | < 95% | Strengthen verification steps |
+
+---
+
+## Codebase Scan Scaling
+
+> Expected scan duration by project size.
+
+| Project Size | Files | Scan Duration (target) | Scan Duration (max) |
+|-------------|-------|----------------------|---------------------|
+| Small | < 100 files | < 3s | 10s |
+| Medium | 100–1000 files | < 10s | 30s |
+| Large | 1000–10000 files | < 30s | 90s |
+| Monorepo | > 10000 files | < 60s | 180s |
+
+**Optimization tips for large codebases:**
+- Use `.gitignore`-aware file listing to skip `node_modules`, `dist`, etc.
+- Limit `find` depth to 2 levels for initial scan (matches `SKILL.md` pre-flight pattern; increase to 3 only for monorepos)
+- Use `git diff` to focus on recently changed files
+- Cache project structure between tasks in the same session
+
+---
+
+## Skill Execution Benchmarks
+
+| Skill | Typical Duration | Token Usage | Success Rate Target |
+|-------|------------------|-------------|---------------------|
+| `debugging/systematic` | 2–5 min | 1500–4000 | > 80% |
+| `debugging/root-cause` | 5–15 min | 2000–10000 | > 70% |
+| `debugging/verification` | 1–3 min | 500–2000 | > 95% |
+| `quality/code-review` | 3–8 min | 1000–5000 | > 85% |
+| `quality/testing` | 3–10 min | 1500–6000 | > 80% |
+| `development/security` | 5–12 min | 1500–8000 | > 75% |
+| `development/backend` | 5–15 min | 2000–8000 | > 75% |
+
+---
+
+## Iron Law Compliance Metrics
+
+| Metric | Target | Measurement Method |
+|--------|--------|--------------------|
+| Evidence citation rate | 100% of recommendations | Count recommendations with/without file:line citations |
+| Hard-Gate completion rate | 100% of tasks | Count tasks that ran Hard-Gate before execution |
+| Verification before completion | 100% of tasks | Count tasks with post-execution verification |
+| Decision trail completeness | > 95% of decisions logged | Audit decision trail entries vs. actions taken |
+| Minimal change adherence | > 90% of tasks | Review changed files vs. task scope |
+
+---
+
+*Performance Benchmarks v1.0.0 — Kilo-Kit*

package/skills/operations/bash-linux/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: bash-linux
+description: Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+---
+
+# Bash Linux Patterns
+
+> Essential patterns for Bash on Linux/macOS.
+
+---
+
+## 1. Operator Syntax
+
+### Chaining Commands
+
+| Operator | Meaning | Example |
+|----------|---------|---------|
+| `;` | Run sequentially | `cmd1; cmd2` |
+| `&&` | Run if previous succeeded | `npm install && npm run dev` |
+| `\|\|` | Run if previous failed | `npm test \|\| echo "Tests failed"` |
+| `\|` | Pipe output | `ls \| grep ".js"` |
+
+---
+
+## 2. File Operations
+
+### Essential Commands
+
+| Task | Command |
+|------|---------|
+| List all | `ls -la` |
+| Find files | `find . -name "*.js" -type f` |
+| File content | `cat file.txt` |
+| First N lines | `head -n 20 file.txt` |
+| Last N lines | `tail -n 20 file.txt` |
+| Follow log | `tail -f log.txt` |
+| Search in files | `grep -r "pattern" --include="*.js"` |
+| File size | `du -sh *` |
+| Disk usage | `df -h` |
+
+---
+
+## 3. Process Management
+
+| Task | Command |
+|------|---------|
+| List processes | `ps aux` |
+| Find by name | `ps aux \| grep node` |
+| Kill by PID | `kill -9 <PID>` |
+| Find port user | `lsof -i :3000` |
+| Kill port | `kill -9 $(lsof -t -i :3000)` |
+| Background | `npm run dev &` |
+| Jobs | `jobs -l` |
+| Bring to front | `fg %1` |
+
+---
+
+## 4. Text Processing
+
+### Core Tools
+
+| Tool | Purpose | Example |
+|------|---------|---------|
+| `grep` | Search | `grep -rn "TODO" src/` |
+| `sed` | Replace | `sed -i 's/old/new/g' file.txt` |
+| `awk` | Extract columns | `awk '{print $1}' file.txt` |
+| `cut` | Cut fields | `cut -d',' -f1 data.csv` |
+| `sort` | Sort lines | `sort -u file.txt` |
+| `uniq` | Unique lines | `sort file.txt \| uniq -c` |
+| `wc` | Count | `wc -l file.txt` |
+
+---
+
+## 5. Environment Variables
+
+| Task | Command |
+|------|---------|
+| View all | `env` or `printenv` |
+| View one | `echo $PATH` |
+| Set temporary | `export VAR="value"` |
+| Set in script | `VAR="value" command` |
+| Add to PATH | `export PATH="$PATH:/new/path"` |
+
+---
+
+## 6. Network
+
+| Task | Command |
+|------|---------|
+| Download | `curl -O https://example.com/file` |
+| API request | `curl -X GET https://api.example.com` |
+| POST JSON | `curl -X POST -H "Content-Type: application/json" -d '{"key":"value"}' URL` |
+| Check port | `nc -zv localhost 3000` |
+| Network info | `ifconfig` or `ip addr` |
+
+---
+
+## 7. Script Template
+
+```bash
+#!/bin/bash
+set -euo pipefail  # Exit on error, undefined var, pipe fail
+
+# Colors (optional)
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+NC='\033[0m'
+
+# Script directory
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# Functions
+log_info() { echo -e "${GREEN}[INFO]${NC} $1"; }
+log_error() { echo -e "${RED}[ERROR]${NC} $1" >&2; }
+
+# Main
+main() {
+    log_info "Starting..."
+    # Your logic here
+    log_info "Done!"
+}
+
+main "$@"
+```
+
+---
+
+## 8. Common Patterns
+
+### Check if command exists
+
+```bash
+if command -v node &> /dev/null; then
+    echo "Node is installed"
+fi
+```
+
+### Default variable value
+
+```bash
+NAME=${1:-"default_value"}
+```
+
+### Read file line by line
+
+```bash
+while IFS= read -r line; do
+    echo "$line"
+done < file.txt
+```
+
+### Loop over files
+
+```bash
+for file in *.js; do
+    echo "Processing $file"
+done
+```
+
+---
+
+## 9. Differences from PowerShell
+
+| Task | PowerShell | Bash |
+|------|------------|------|
+| List files | `Get-ChildItem` | `ls -la` |
+| Find files | `Get-ChildItem -Recurse` | `find . -type f` |
+| Environment | `$env:VAR` | `$VAR` |
+| String concat | `"$a$b"` | `"$a$b"` (same) |
+| Null check | `if ($x)` | `if [ -n "$x" ]` |
+| Pipeline | Object-based | Text-based |
+
+---
+
+## 10. Error Handling
+
+### Set options
+
+```bash
+set -e          # Exit on error
+set -u          # Exit on undefined variable
+set -o pipefail # Exit on pipe failure
+set -x          # Debug: print commands
+```
+
+### Trap for cleanup
+
+```bash
+cleanup() {
+    echo "Cleaning up..."
+    rm -f /tmp/tempfile
+}
+trap cleanup EXIT
+```
+
+---
+
+> **Remember:** Bash is text-based. Use `&&` for success chains, `set -e` for safety, and quote your variables!