@mrciphersmith/keryx 0.2.9

package/src/gdskills/bundled/skills/quality/security-audit/SKILL.claude.md

@@ -0,0 +1,40 @@
+---
+description: Security audit — npm/bun audit, dependency vulnerabilities, secrets scan
+allowed-tools: Bash(*)
+---
+
+## Context
+
+- Package manager: !`ls bun.lockb yarn.lock pnpm-lock.yaml package-lock.json 2>/dev/null | head -1 || echo "unknown"`
+- Bun version: !`bun --version 2>/dev/null || echo "n/a"`
+- Dependencies: !`cat package.json 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); print(len(d.get('dependencies',{})), 'prod,', len(d.get('devDependencies',{})), 'dev')" 2>/dev/null || echo "unknown"`
+
+## Your task
+
+Run a comprehensive security audit.
+
+### Step 1 — Dependency vulnerabilities
+- `bun.lockb` → `bun audit`
+- `package-lock.json` → `npm audit --json`
+- `yarn.lock` → `yarn audit`
+
+Group: **critical → high → moderate → low**
+
+### Step 2 — Outdated packages
+`bun outdated 2>/dev/null || npm outdated` — flag 2+ major versions behind
+
+### Step 3 — Secrets scan
+```bash
+git log --all --full-history -- "*.env" "*.key" "*.pem" 2>/dev/null | head -20
+grep -r "password\s*=\s*['\"][^'\"]\|api_key\s*=\s*['\"][^'\"]\|secret\s*=\s*['\"][^'\"]" \
+  --include="*.ts" --include="*.js" -l . 2>/dev/null | grep -v node_modules
+```
+
+### Step 4 — Docker image scan (if Dockerfile present)
+`docker scout cves $(docker build -q .) 2>/dev/null || echo "Docker Scout not available"`
+
+### Report
+- Total by severity
+- Top 3 critical/high with CVE
+- Immediate actions
+- Packages safe to ignore (dev-only)

package/src/gdskills/bundled/skills/quality/security-audit/SKILL.codex.md

@@ -0,0 +1,61 @@
+---
+name: security-audit
+description: "Security audit: runs npm/bun/yarn audit for dependency vulnerabilities, scans for accidentally committed secrets, checks Docker images if present. Groups findings by severity (critical → high → moderate → low). Produces remediation report."
+triggers:
+  - "Security audit"
+  - "Check vulnerabilities"
+  - "Audit dependencies"
+  - "Security scan"
+  - "Check for CVEs"
+  - "npm audit"
+  - "Dependency vulnerabilities"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "quality"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Security Audit
+
+## Purpose
+
+Comprehensive security audit covering dependency vulnerabilities, secrets in code/git history, and container image scanning. Produces a prioritized remediation report.
+
+**Input:** None (scans current project)
+**Output:** Severity-grouped vulnerability report with remediation steps
+
+## When to Use
+
+- Before a release
+- After adding new dependencies
+- Periodic security review
+
+## Steps
+
+### Step 1 — Dependency vulnerabilities
+Auto-detect: `bun.lockb` → `bun audit` | `package-lock.json` → `npm audit --json` | `yarn.lock` → `yarn audit`
+
+Group by severity: **critical → high → moderate → low**
+
+### Step 2 — Outdated packages
+Run `bun outdated` or `npm outdated`. Flag packages more than 2 major versions behind.
+
+### Step 3 — Secrets scan
+- Check git history for `.env`, `.key`, `.pem` files
+- Grep source for hardcoded passwords/API keys/secrets (excluding node_modules)
+
+### Step 4 — Docker image scan
+If Dockerfile present and Docker available: `docker scout cves`
+
+### Report
+- Total by severity
+- Top 3 critical/high with CVE
+- Recommended immediate actions
+- Packages safe to ignore (dev-only, not reachable in prod)
+
+## Rules
+
+- Distinguish prod vs dev-only vulnerabilities
+- Never suggest `npm audit fix --force` without explaining what it changes

package/src/gdskills/bundled/skills/quality/security-audit/SKILL.cursor.md

@@ -0,0 +1,61 @@
+---
+name: security-audit
+description: "Security audit: runs npm/bun/yarn audit for dependency vulnerabilities, scans for accidentally committed secrets, checks Docker images if present. Groups findings by severity (critical → high → moderate → low). Produces remediation report."
+triggers:
+  - "Security audit"
+  - "Check vulnerabilities"
+  - "Audit dependencies"
+  - "Security scan"
+  - "Check for CVEs"
+  - "npm audit"
+  - "Dependency vulnerabilities"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "quality"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Security Audit
+
+## Purpose
+
+Comprehensive security audit covering dependency vulnerabilities, secrets in code/git history, and container image scanning. Produces a prioritized remediation report.
+
+**Input:** None (scans current project)
+**Output:** Severity-grouped vulnerability report with remediation steps
+
+## When to Use
+
+- Before a release
+- After adding new dependencies
+- Periodic security review
+
+## Steps
+
+### Step 1 — Dependency vulnerabilities
+Auto-detect: `bun.lockb` → `bun audit` | `package-lock.json` → `npm audit --json` | `yarn.lock` → `yarn audit`
+
+Group by severity: **critical → high → moderate → low**
+
+### Step 2 — Outdated packages
+Run `bun outdated` or `npm outdated`. Flag packages more than 2 major versions behind.
+
+### Step 3 — Secrets scan
+- Check git history for `.env`, `.key`, `.pem` files
+- Grep source for hardcoded passwords/API keys/secrets (excluding node_modules)
+
+### Step 4 — Docker image scan
+If Dockerfile present and Docker available: `docker scout cves`
+
+### Report
+- Total by severity
+- Top 3 critical/high with CVE
+- Recommended immediate actions
+- Packages safe to ignore (dev-only, not reachable in prod)
+
+## Rules
+
+- Distinguish prod vs dev-only vulnerabilities
+- Never suggest `npm audit fix --force` without explaining what it changes

package/src/gdskills/bundled/skills/quality/security-audit/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: security-audit
+description: "Use when checking for dependency vulnerabilities, accidentally committed secrets, or security issues in Docker images."
+triggers:
+  - "Security audit"
+  - "Check vulnerabilities"
+  - "Audit dependencies"
+  - "Security scan"
+  - "Check for CVEs"
+  - "npm audit"
+  - "Dependency vulnerabilities"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "quality"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Security Audit
+
+## Purpose
+
+Comprehensive security audit covering dependency vulnerabilities, secrets in code/git history, and container image scanning. Produces a prioritized remediation report.
+
+**Input:** None (scans current project)
+**Output:** Severity-grouped vulnerability report with remediation steps
+
+## When to Use
+
+- Before a release
+- After adding new dependencies
+- Periodic security review
+
+## Steps
+
+### Step 1 — Dependency vulnerabilities
+Auto-detect: `bun.lockb` → `bun audit` | `package-lock.json` → `npm audit --json` | `yarn.lock` → `yarn audit`
+
+Group by severity: **critical → high → moderate → low**
+
+### Step 2 — Outdated packages
+Run `bun outdated` or `npm outdated`. Flag packages more than 2 major versions behind.
+
+### Step 3 — Secrets scan
+- Check git history for `.env`, `.key`, `.pem` files
+- Grep source for hardcoded passwords/API keys/secrets (excluding node_modules)
+
+### Step 4 — Docker image scan
+If Dockerfile present and Docker available: `docker scout cves`
+
+### Report
+- Total by severity
+- Top 3 critical/high with CVE
+- Recommended immediate actions
+- Packages safe to ignore (dev-only, not reachable in prod)
+
+## Rules
+
+- Distinguish prod vs dev-only vulnerabilities
+- Never suggest `npm audit fix --force` without explaining what it changes

package/src/gdskills/bundled/skills/quality/test-gen/SKILL.claude.md

@@ -0,0 +1,30 @@
+---
+description: Auto-generate tests for a specified file or module
+allowed-tools: Bash(*), Read(*), Write(*), Glob(*)
+---
+
+## Context
+
+- Test framework: !`cat package.json 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); deps={**d.get('dependencies',{}),**d.get('devDependencies',{})}; print(next((k for k in ['bun:test','vitest','jest'] if k in str(deps)), 'unknown'))" 2>/dev/null || echo "unknown"`
+- Existing tests: !`find . -name "*.test.ts" -not -path "*/node_modules/*" 2>/dev/null | head -5 || echo "none"`
+- Sample test style: !`find . -name "*.test.ts" -not -path "*/node_modules/*" 2>/dev/null | head -1 | xargs head -30 2>/dev/null || echo "none"`
+
+## Your task
+
+Generate tests for: $ARGUMENTS
+
+1. **Read** the target file completely
+2. **Check** for existing tests (`<name>.test.ts` or `__tests__/<name>.ts`)
+3. **Plan** test cases:
+   - Happy path for each export
+   - Edge cases: empty, null, boundary values
+   - Error cases: invalid input, exceptions, DB errors
+   - API routes: each method + auth + 200/400/401/404/500
+4. **Write** tests matching existing style:
+   - bun:test → `import { describe, test, expect, mock } from "bun:test"`
+   - jest/vitest → respective imports
+   - Mock external dependencies at correct boundary
+5. **Write** test file to `<name>.test.ts` (same dir) or `__tests__/` if that's the convention
+6. **Run** and fix: `bun test <file> 2>/dev/null || npx jest <file> 2>/dev/null`
+
+Report: tests generated, estimated coverage, cases needing manual work.

package/src/gdskills/bundled/skills/quality/test-gen/SKILL.codex.md

@@ -0,0 +1,75 @@
+---
+name: test-gen
+description: "Auto-generate tests for a file or module. Discovers project testing patterns (Jest/Vitest/Pytest), analyzes code structure, creates unit and integration tests matching existing conventions. Verifies all tests pass."
+triggers:
+  - "/test-gen"
+  - "Generate tests"
+  - "Write tests for"
+  - "Add tests"
+  - "Create test file"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "testing"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Test Generator
+
+Auto-generate tests for specified files or modules.
+
+## Arguments
+
+- `/test-gen <file>` — generate tests for specific file
+- `/test-gen <directory>` — tests for all files in directory
+- `/test-gen --integration` — focus on integration tests
+- `/test-gen --coverage` — run with coverage report after
+
+## Workflow
+
+### Step 1: Understand the Target
+1. Read the target file(s)
+2. Identify: exports, functions, classes, API endpoints, React components
+3. Map dependencies and side effects
+
+### Step 2: Discover Testing Patterns
+1. Find test framework (Jest, Vitest, Pytest) from configs
+2. Find test file location convention from existing tests
+3. Read 1-2 neighboring test files to match: import style, describe/it structure, mock patterns, assertion style
+
+### Step 3: Plan Test Cases
+
+**Functions:** happy path, edge cases (empty/null/zero/negative), error cases, boundary values
+
+**Components:** renders, props, interactions, conditional rendering, states
+
+**Endpoints:** success (200), validation (400), not found (404), auth (401/403)
+
+**Classes:** constructor, methods, state transitions, errors
+
+### Step 4: Generate
+1. Create test file at correct path (matching convention)
+2. Write imports matching project style
+3. Generate grouped test cases with appropriate mocks
+4. One assertion per test where practical
+
+### Step 5: Verify
+```bash
+npx jest <test-file> --no-coverage
+```
+Fix failing tests (max 3 iterations) — fix the test, not the source.
+
+### Step 6: Report
+```
+✅ Generated: src/utils/__tests__/helper.test.ts
+   - 12 test cases, all passing ✓
+```
+
+## Rules
+
+- ALWAYS match existing test patterns in the project
+- NEVER modify source code — only test files
+- Mock external dependencies, not internal modules
+- Meaningful test descriptions
+- If no test framework detected, suggest installing one

package/src/gdskills/bundled/skills/quality/test-gen/SKILL.cursor.md

@@ -0,0 +1,75 @@
+---
+name: test-gen
+description: "Auto-generate tests for a file or module. Discovers project testing patterns (Jest/Vitest/Pytest), analyzes code structure, creates unit and integration tests matching existing conventions. Verifies all tests pass."
+triggers:
+  - "/test-gen"
+  - "Generate tests"
+  - "Write tests for"
+  - "Add tests"
+  - "Create test file"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "testing"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Test Generator
+
+Auto-generate tests for specified files or modules.
+
+## Arguments
+
+- `/test-gen <file>` — generate tests for specific file
+- `/test-gen <directory>` — tests for all files in directory
+- `/test-gen --integration` — focus on integration tests
+- `/test-gen --coverage` — run with coverage report after
+
+## Workflow
+
+### Step 1: Understand the Target
+1. Read the target file(s)
+2. Identify: exports, functions, classes, API endpoints, React components
+3. Map dependencies and side effects
+
+### Step 2: Discover Testing Patterns
+1. Find test framework (Jest, Vitest, Pytest) from configs
+2. Find test file location convention from existing tests
+3. Read 1-2 neighboring test files to match: import style, describe/it structure, mock patterns, assertion style
+
+### Step 3: Plan Test Cases
+
+**Functions:** happy path, edge cases (empty/null/zero/negative), error cases, boundary values
+
+**Components:** renders, props, interactions, conditional rendering, states
+
+**Endpoints:** success (200), validation (400), not found (404), auth (401/403)
+
+**Classes:** constructor, methods, state transitions, errors
+
+### Step 4: Generate
+1. Create test file at correct path (matching convention)
+2. Write imports matching project style
+3. Generate grouped test cases with appropriate mocks
+4. One assertion per test where practical
+
+### Step 5: Verify
+```bash
+npx jest <test-file> --no-coverage
+```
+Fix failing tests (max 3 iterations) — fix the test, not the source.
+
+### Step 6: Report
+```
+✅ Generated: src/utils/__tests__/helper.test.ts
+   - 12 test cases, all passing ✓
+```
+
+## Rules
+
+- ALWAYS match existing test patterns in the project
+- NEVER modify source code — only test files
+- Mock external dependencies, not internal modules
+- Meaningful test descriptions
+- If no test framework detected, suggest installing one

package/src/gdskills/bundled/skills/quality/test-gen/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: test-gen
+description: "Use when unit or integration tests need to be written for a specific file or module."
+triggers:
+  - "/test-gen"
+  - "Generate tests"
+  - "Write tests for"
+  - "Add tests"
+  - "Create test file"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "testing"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Test Generator
+
+Auto-generate tests for specified files or modules.
+
+## Arguments
+
+- `/test-gen <file>` — generate tests for specific file
+- `/test-gen <directory>` — tests for all files in directory
+- `/test-gen --integration` — focus on integration tests
+- `/test-gen --coverage` — run with coverage report after
+
+## Workflow
+
+### Step 1: Understand the Target
+1. Read the target file(s)
+2. Identify: exports, functions, classes, API endpoints, React components
+3. Map dependencies and side effects
+
+### Step 2: Discover Testing Patterns
+1. Find test framework (Jest, Vitest, Pytest) from configs
+2. Find test file location convention from existing tests
+3. Read 1-2 neighboring test files to match: import style, describe/it structure, mock patterns, assertion style
+
+### Step 3: Plan Test Cases
+
+**Functions:** happy path, edge cases (empty/null/zero/negative), error cases, boundary values
+
+**Components:** renders, props, interactions, conditional rendering, states
+
+**Endpoints:** success (200), validation (400), not found (404), auth (401/403)
+
+**Classes:** constructor, methods, state transitions, errors
+
+### Step 4: Generate
+1. Create test file at correct path (matching convention)
+2. Write imports matching project style
+3. Generate grouped test cases with appropriate mocks
+4. One assertion per test where practical
+
+### Step 5: Verify
+```bash
+npx jest <test-file> --no-coverage
+```
+Fix failing tests (max 3 iterations) — fix the test, not the source.
+
+### Step 6: Report
+```
+✅ Generated: src/utils/__tests__/helper.test.ts
+   - 12 test cases, all passing ✓
+```
+
+## Rules
+
+- ALWAYS match existing test patterns in the project
+- NEVER modify source code — only test files
+- Mock external dependencies, not internal modules
+- Meaningful test descriptions
+- If no test framework detected, suggest installing one

package/src/gdskills/bundled/skills/quality/tests-creator/SKILL.codex.md

@@ -0,0 +1,64 @@
+---
+name: tests-creator
+description: "Converts acceptance criteria into failing test stubs (RED phase of TDD) before any implementation. Autonomous sub-agent — runs between issue-analyzer and task-implementer. Use when: generating test specs from acceptance criteria, enforcing TDD in the implementation pipeline."
+triggers:
+  - "Create tests"
+  - "Write tests first"
+  - "Generate test specs"
+  - "Tests before implementation"
+  - "TDD test stubs"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "testing"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode"
+---
+
+# Tests Creator
+
+## Purpose
+
+Converts acceptance criteria into failing test stubs that task-implementer will make pass.
+
+**Input:** Task with `acceptance_criteria` + codebase path
+**Output:** Failing test files (RED phase) + `TEST_CASE_SPECS` report
+
+## Execution Steps
+
+1. **Detect framework** — check `package.json`, read existing test files
+2. **Map criteria** — each criterion → happy path + edge cases + error paths
+3. **Generate stubs** — write test files with forward-declared assertions (will fail)
+4. **Commit** — `git commit -m "test: add failing stubs for <task>"`
+5. **Verify RED** — run tests, confirm all fail
+6. **Report** — emit `TEST_CASE_SPECS` block
+
+## Output Template
+
+```
+TEST_CASE_SPECS:
+  framework: <vitest|jest|pytest|bun:test>
+  test_files:
+    - path: <test file path>
+      target_module: <source file to implement>
+      test_count: <N>
+      tests:
+        - id: test-<N>
+          description: "<it description>"
+          criterion: "<acceptance criterion>"
+          type: happy_path | edge_case | error_path
+          status: written
+  run_command: "<test command>"
+  expected_result: "all failing (RED phase)"
+
+STATUS: DONE
+tests_written: <N>
+all_criteria_covered: true | false
+```
+
+## Iron Laws
+- NEVER write implementation code — only test files
+- Tests MUST FAIL before reporting DONE
+- Every acceptance criterion needs ≥1 test
+
+See full workflow: `.metaproject/skills/gdskills/quality/tests-creator/SKILL.md`

package/src/gdskills/bundled/skills/quality/tests-creator/SKILL.cursor.md

@@ -0,0 +1,74 @@
+---
+name: tests-creator
+description: "Converts acceptance criteria into failing test stubs (RED phase of TDD) before any implementation. Autonomous sub-agent — runs between issue-analyzer and task-implementer. Use when: generating test specs from acceptance criteria, enforcing TDD in the implementation pipeline."
+triggers:
+  - "Create tests"
+  - "Write tests first"
+  - "Generate test specs"
+  - "Tests before implementation"
+  - "TDD test stubs"
+  - "Convert criteria to tests"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "testing"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode"
+---
+
+# Tests Creator
+
+## Purpose
+
+Converts acceptance criteria into concrete, failing test stubs **before any implementation code is written**. Enforces the RED phase of TDD.
+
+**Input:** Task object with `acceptance_criteria` + codebase path
+**Output:** Committed test files (RED) + `test_case_specs` block for `task-implementer`
+
+## When to Use
+
+- Between `issue-analyzer` and `task-implementer` in the TDD pipeline
+- Before writing any implementation code for a task
+
+## Quick Reference
+
+### Phase Summary
+1. **DETECT** — find test framework, read existing tests for conventions
+2. **ANALYZE** — map each acceptance criterion to happy path + edge + error scenarios
+3. **GENERATE** — write failing test stubs using forward-declared API
+4. **REPORT** — emit `TEST_CASE_SPECS` block
+
+### Key Rule
+Tests MUST FAIL before implementation. Run `<test command>` to verify RED state.
+
+### Output Format
+```
+TEST_CASE_SPECS:
+  framework: vitest
+  test_files:
+    - path: src/__tests__/UserValidator.test.ts
+      target_module: src/services/UserValidator.ts
+      test_count: 4
+      tests:
+        - id: test-1
+          description: "should accept valid email address"
+          criterion: "User can register with valid email"
+          type: happy_path
+          status: written
+  run_command: "bun test src/__tests__/UserValidator.test.ts"
+  expected_result: "all failing (RED phase)"
+
+STATUS: DONE
+tests_written: 4
+all_criteria_covered: true
+```
+
+### Status Protocol
+```
+STATUS: DONE            — all criteria covered, tests committed, RED verified
+STATUS: DONE_WITH_CONCERNS — some criteria ambiguous, tests written with assumptions
+STATUS: BLOCKED         — cannot determine test framework or API shape
+STATUS: NEEDS_CONTEXT   — acceptance criteria missing, need task description
+```
+
+See full workflow in `.metaproject/skills/gdskills/quality/tests-creator/SKILL.md`