@mrciphersmith/keryx 0.2.9

package/src/gdskills/bundled/skills/quality/perf-check/SKILL.codex.md

@@ -0,0 +1,83 @@
+---
+name: perf-check
+description: "Performance analysis: bundle size measurement, Lighthouse audit, dependency weight analysis, code-level anti-pattern detection (N+1, missing memoization, heavy imports). Produces prioritized report with optimization suggestions."
+triggers:
+  - "/perf-check"
+  - "Check performance"
+  - "Bundle size"
+  - "Lighthouse"
+  - "Why is it slow"
+  - "Optimize performance"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "performance"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Performance Check
+
+Analyze and report on project performance metrics.
+
+## Arguments
+
+- `/perf-check` — full analysis
+- `/perf-check --bundle` — bundle size only
+- `/perf-check --lighthouse <url>` — Lighthouse audit
+- `/perf-check --deps` — dependency weight analysis
+- `/perf-check --code` — code-level pattern check
+
+## Workflow
+
+### Phase 1: Detect Scope
+- **Frontend**: bundle size, lighthouse, dependency weight
+- **Backend**: startup time, memory, dependency weight
+- **Fullstack**: both
+
+### Phase 2: Bundle Analysis
+- Build and measure output: `du -sh dist/ build/ .next/`
+- Check largest dependencies: `npx -y cost-of-modules`
+- Identify tree-shaking opportunities
+
+### Phase 3: Lighthouse (if URL available)
+```bash
+npx -y lighthouse <url> --output json --chrome-flags="--headless --no-sandbox"
+```
+
+### Phase 4: Dependency Analysis
+Flag heavy dependencies:
+- `moment` → `dayjs` or `date-fns`
+- `lodash` (full) → `lodash-es` or individual imports
+- `aws-sdk` v2 → `@aws-sdk/client-*` v3
+
+### Phase 5: Code Anti-patterns
+- N+1 queries (loop with await)
+- `JSON.parse(JSON.stringify())` for clone
+- Missing `useMemo`/`useCallback` on expensive operations
+- Sync file ops in request handlers
+- Missing database indexes
+
+### Phase 6: Report
+
+```markdown
+# Performance Report
+
+## Bundle
+- Total: 1.2MB (gzipped: 380KB)
+
+## Issues Found
+🔴 moment.js adds 230KB — replace with dayjs (2KB)
+🟡 Full lodash import — use lodash-es
+
+## Recommendations (by impact)
+1. Replace moment → dayjs (saves ~228KB)
+2. Code-split vendor chunk
+```
+
+## Rules
+
+- Don't make changes — only analyze and report
+- Sort recommendations by estimated impact
+- Include specific numbers (KB saved, ms improved)
+- Suggest alternatives for every heavy dependency flagged

package/src/gdskills/bundled/skills/quality/perf-check/SKILL.cursor.md

@@ -0,0 +1,83 @@
+---
+name: perf-check
+description: "Performance analysis: bundle size measurement, Lighthouse audit, dependency weight analysis, code-level anti-pattern detection (N+1, missing memoization, heavy imports). Produces prioritized report with optimization suggestions."
+triggers:
+  - "/perf-check"
+  - "Check performance"
+  - "Bundle size"
+  - "Lighthouse"
+  - "Why is it slow"
+  - "Optimize performance"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "performance"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Performance Check
+
+Analyze and report on project performance metrics.
+
+## Arguments
+
+- `/perf-check` — full analysis
+- `/perf-check --bundle` — bundle size only
+- `/perf-check --lighthouse <url>` — Lighthouse audit
+- `/perf-check --deps` — dependency weight analysis
+- `/perf-check --code` — code-level pattern check
+
+## Workflow
+
+### Phase 1: Detect Scope
+- **Frontend**: bundle size, lighthouse, dependency weight
+- **Backend**: startup time, memory, dependency weight
+- **Fullstack**: both
+
+### Phase 2: Bundle Analysis
+- Build and measure output: `du -sh dist/ build/ .next/`
+- Check largest dependencies: `npx -y cost-of-modules`
+- Identify tree-shaking opportunities
+
+### Phase 3: Lighthouse (if URL available)
+```bash
+npx -y lighthouse <url> --output json --chrome-flags="--headless --no-sandbox"
+```
+
+### Phase 4: Dependency Analysis
+Flag heavy dependencies:
+- `moment` → `dayjs` or `date-fns`
+- `lodash` (full) → `lodash-es` or individual imports
+- `aws-sdk` v2 → `@aws-sdk/client-*` v3
+
+### Phase 5: Code Anti-patterns
+- N+1 queries (loop with await)
+- `JSON.parse(JSON.stringify())` for clone
+- Missing `useMemo`/`useCallback` on expensive operations
+- Sync file ops in request handlers
+- Missing database indexes
+
+### Phase 6: Report
+
+```markdown
+# Performance Report
+
+## Bundle
+- Total: 1.2MB (gzipped: 380KB)
+
+## Issues Found
+🔴 moment.js adds 230KB — replace with dayjs (2KB)
+🟡 Full lodash import — use lodash-es
+
+## Recommendations (by impact)
+1. Replace moment → dayjs (saves ~228KB)
+2. Code-split vendor chunk
+```
+
+## Rules
+
+- Don't make changes — only analyze and report
+- Sort recommendations by estimated impact
+- Include specific numbers (KB saved, ms improved)
+- Suggest alternatives for every heavy dependency flagged

package/src/gdskills/bundled/skills/quality/perf-check/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: perf-check
+description: "Use when measuring bundle size, detecting performance regressions, auditing slow queries, or investigating why something is slow."
+triggers:
+  - "/perf-check"
+  - "Check performance"
+  - "Bundle size"
+  - "Lighthouse"
+  - "Why is it slow"
+  - "Optimize performance"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "performance"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Performance Check
+
+Analyze and report on project performance metrics.
+
+## Arguments
+
+- `/perf-check` — full analysis
+- `/perf-check --bundle` — bundle size only
+- `/perf-check --lighthouse <url>` — Lighthouse audit
+- `/perf-check --deps` — dependency weight analysis
+- `/perf-check --code` — code-level pattern check
+
+## Workflow
+
+### Phase 1: Detect Scope
+- **Frontend**: bundle size, lighthouse, dependency weight
+- **Backend**: startup time, memory, dependency weight
+- **Fullstack**: both
+
+### Phase 2: Bundle Analysis
+- Build and measure output: `du -sh dist/ build/ .next/`
+- Check largest dependencies: `npx -y cost-of-modules`
+- Identify tree-shaking opportunities
+
+### Phase 3: Lighthouse (if URL available)
+```bash
+npx -y lighthouse <url> --output json --chrome-flags="--headless --no-sandbox"
+```
+
+### Phase 4: Dependency Analysis
+Flag heavy dependencies:
+- `moment` → `dayjs` or `date-fns`
+- `lodash` (full) → `lodash-es` or individual imports
+- `aws-sdk` v2 → `@aws-sdk/client-*` v3
+
+### Phase 5: Code Anti-patterns
+- N+1 queries (loop with await)
+- `JSON.parse(JSON.stringify())` for clone
+- Missing `useMemo`/`useCallback` on expensive operations
+- Sync file ops in request handlers
+- Missing database indexes
+
+### Phase 6: Report
+
+```markdown
+# Performance Report
+
+## Bundle
+- Total: 1.2MB (gzipped: 380KB)
+
+## Issues Found
+🔴 moment.js adds 230KB — replace with dayjs (2KB)
+🟡 Full lodash import — use lodash-es
+
+## Recommendations (by impact)
+1. Replace moment → dayjs (saves ~228KB)
+2. Code-split vendor chunk
+```
+
+## Rules
+
+- Don't make changes — only analyze and report
+- Sort recommendations by estimated impact
+- Include specific numbers (KB saved, ms improved)
+- Suggest alternatives for every heavy dependency flagged

package/src/gdskills/bundled/skills/quality/pr/SKILL.codex.md

@@ -0,0 +1,75 @@
+---
+name: pr
+description: "Smart Pull Request creation: analyzes all branch commits, generates structured title and description with Summary/Changes/Test plan, creates PR via gh CLI. Auto-pushes if branch not on remote."
+triggers:
+  - "/pr"
+  - "Create PR"
+  - "Open pull request"
+  - "Create pull request"
+  - "Make PR"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Smart PR Creation
+
+Create a well-documented GitHub Pull Request from current branch.
+
+## Workflow
+
+### Phase 1: Gather Context
+Run in parallel:
+1. `git status` — check for uncommitted changes
+2. `git branch --show-current` — current branch name
+3. `git log --oneline main..HEAD` (or master) — all commits in this branch
+4. `git diff main...HEAD --stat` — changed files summary
+
+### Phase 2: Pre-checks
+- If there are uncommitted changes → ask if the user wants to commit first
+- If branch is not pushed → push it with `-u origin`
+- If already on main/master → error: "Create a feature branch first"
+
+### Phase 3: Analyze Changes
+Analyze ALL commits and changes (not just the latest):
+- `git diff main...HEAD` for the full diff
+- Understand the scope: new feature, bugfix, refactor, etc.
+
+### Phase 4: Generate & Create PR
+Generate structured PR:
+- **Title**: short, under 70 chars, descriptive
+- **Body**: Summary + Changes + Test plan
+
+```bash
+gh pr create --title "title" --body "$(cat <<'EOF'
+## Summary
+<bullet points>
+
+## Changes
+<key changes by area>
+
+## Test plan
+<how to verify>
+EOF
+)"
+```
+
+### Phase 5: Report
+Return the PR URL to the user.
+
+## Arguments
+
+- `/pr` — create PR to default branch (main/master)
+- `/pr --draft` — create as draft PR
+- `/pr --base <branch>` — target specific base branch
+- `/pr <title>` — use provided title instead of generating one
+
+## Rules
+
+- NEVER create empty PRs
+- Always analyze ALL commits, not just the last one
+- If the branch has linked GitHub issues, reference them in the body
+- Ask user for confirmation before creating if there are 10+ commits

package/src/gdskills/bundled/skills/quality/pr/SKILL.cursor.md

@@ -0,0 +1,75 @@
+---
+name: pr
+description: "Smart Pull Request creation: analyzes all branch commits, generates structured title and description with Summary/Changes/Test plan, creates PR via gh CLI. Auto-pushes if branch not on remote."
+triggers:
+  - "/pr"
+  - "Create PR"
+  - "Open pull request"
+  - "Create pull request"
+  - "Make PR"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Smart PR Creation
+
+Create a well-documented GitHub Pull Request from current branch.
+
+## Workflow
+
+### Phase 1: Gather Context
+Run in parallel:
+1. `git status` — check for uncommitted changes
+2. `git branch --show-current` — current branch name
+3. `git log --oneline main..HEAD` (or master) — all commits in this branch
+4. `git diff main...HEAD --stat` — changed files summary
+
+### Phase 2: Pre-checks
+- If there are uncommitted changes → ask if the user wants to commit first
+- If branch is not pushed → push it with `-u origin`
+- If already on main/master → error: "Create a feature branch first"
+
+### Phase 3: Analyze Changes
+Analyze ALL commits and changes (not just the latest):
+- `git diff main...HEAD` for the full diff
+- Understand the scope: new feature, bugfix, refactor, etc.
+
+### Phase 4: Generate & Create PR
+Generate structured PR:
+- **Title**: short, under 70 chars, descriptive
+- **Body**: Summary + Changes + Test plan
+
+```bash
+gh pr create --title "title" --body "$(cat <<'EOF'
+## Summary
+<bullet points>
+
+## Changes
+<key changes by area>
+
+## Test plan
+<how to verify>
+EOF
+)"
+```
+
+### Phase 5: Report
+Return the PR URL to the user.
+
+## Arguments
+
+- `/pr` — create PR to default branch (main/master)
+- `/pr --draft` — create as draft PR
+- `/pr --base <branch>` — target specific base branch
+- `/pr <title>` — use provided title instead of generating one
+
+## Rules
+
+- NEVER create empty PRs
+- Always analyze ALL commits, not just the last one
+- If the branch has linked GitHub issues, reference them in the body
+- Ask user for confirmation before creating if there are 10+ commits

package/src/gdskills/bundled/skills/quality/pr/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: pr
+description: "Use when opening a pull request for the current branch."
+triggers:
+  - "/pr"
+  - "Create PR"
+  - "Open pull request"
+  - "Create pull request"
+  - "Make PR"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Smart PR Creation
+
+Create a well-documented GitHub Pull Request from current branch.
+
+## Workflow
+
+### Phase 1: Gather Context
+Run in parallel:
+1. `git status` — check for uncommitted changes
+2. `git branch --show-current` — current branch name
+3. `git log --oneline main..HEAD` (or master) — all commits in this branch
+4. `git diff main...HEAD --stat` — changed files summary
+
+### Phase 2: Pre-checks
+- If there are uncommitted changes → ask if the user wants to commit first
+- If branch is not pushed → push it with `-u origin`
+- If already on main/master → error: "Create a feature branch first"
+
+### Phase 3: Analyze Changes
+Analyze ALL commits and changes (not just the latest):
+- `git diff main...HEAD` for the full diff
+- Understand the scope: new feature, bugfix, refactor, etc.
+
+### Phase 4: Generate & Create PR
+Generate structured PR:
+- **Title**: short, under 70 chars, descriptive
+- **Body**: Summary + Changes + Test plan
+
+```bash
+gh pr create --title "title" --body "$(cat <<'EOF'
+## Summary
+<bullet points>
+
+## Changes
+<key changes by area>
+
+## Test plan
+<how to verify>
+EOF
+)"
+```
+
+### Phase 5: Report
+Return the PR URL to the user.
+
+## Arguments
+
+- `/pr` — create PR to default branch (main/master)
+- `/pr --draft` — create as draft PR
+- `/pr --base <branch>` — target specific base branch
+- `/pr <title>` — use provided title instead of generating one
+
+## Rules
+
+- NEVER create empty PRs
+- Always analyze ALL commits, not just the last one
+- If the branch has linked GitHub issues, reference them in the body
+- Ask user for confirmation before creating if there are 10+ commits