@mrciphersmith/keryx 0.2.9

package/src/gdskills/bundled/skills/platform/claude-md-management/SKILL.codex.md

@@ -0,0 +1,87 @@
+---
+name: claude-md-management
+description: "Capture session learnings and persist into CLAUDE.md files. Extracts coding patterns, conventions, commands, and gotchas discovered during work. Classifies into project-level vs global vs personal CLAUDE.md. Shows diff preview before applying."
+triggers:
+  - "/revise-claude-md"
+  - "Update claude md"
+  - "Save learnings"
+  - "Update project instructions"
+  - "Add to CLAUDE.md"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "configuration"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# CLAUDE.md Management
+
+Capture session insights and persist them into the appropriate CLAUDE.md file.
+
+## Arguments
+
+- `/revise-claude-md` — analyze session and propose updates
+- `/revise-claude-md "specific thing"` — add a specific entry
+- `/revise-claude-md --auto` — apply without asking (for pipelines)
+
+## Workflow
+
+### Step 1: Collect Session Insights
+Analyze the current conversation for:
+- Coding patterns discovered or established
+- Project conventions learned (naming, structure, testing)
+- Build/deploy commands that work
+- Gotchas and pitfalls encountered
+- Architecture decisions made
+- Tool configurations set up
+
+### Step 2: Read Current CLAUDE.md Files
+1. Project-level: `<project-root>/CLAUDE.md`
+2. User-level: `~/.claude/CLAUDE.md`
+3. Project-specific user-level: `~/.claude/projects/<project-path>/CLAUDE.md`
+
+### Step 3: Classify Each Insight
+
+| Type | Target |
+|------|--------|
+| Project conventions, build commands | `<project>/CLAUDE.md` |
+| Global preferences, workflow rules | `~/.claude/CLAUDE.md` |
+| Project-specific personal notes | `~/.claude/projects/<path>/CLAUDE.md` |
+
+### Step 4: Propose Changes
+Present diff preview:
+```
+📝 Proposed CLAUDE.md updates:
+
+[project] CLAUDE.md:
++ ## Build Commands
++ - `npm run dev` — start dev server on port 3000
+
+[global] ~/.claude/CLAUDE.md:
++ ## Preferences
++ - Always use conventional commits
+```
+
+### Step 5: Apply (after user approval)
+1. Edit existing sections or append new sections
+2. Keep organized with clear `##` headers
+3. Avoid duplication — merge with existing
+4. Remove outdated entries if contradicted
+
+## Formatting Rules for CLAUDE.md
+
+- Use `##` headers for sections
+- Use `-` bullet lists for items
+- Keep entries concise (1 line each)
+- Group by: Commands, Conventions, Architecture, Gotchas
+- No frontmatter in CLAUDE.md files
+- CLAUDE.md should be practical — commands you run, not documentation
+
+## Rules
+
+- ALWAYS show proposed changes before applying
+- NEVER remove existing entries without explanation
+- NEVER add entries that duplicate what's already there
+- Keep CLAUDE.md files under 100 lines
+- Prefer project-level for project-specific things

package/src/gdskills/bundled/skills/platform/claude-md-management/SKILL.cursor.md

@@ -0,0 +1,87 @@
+---
+name: claude-md-management
+description: "Capture session learnings and persist into CLAUDE.md files. Extracts coding patterns, conventions, commands, and gotchas discovered during work. Classifies into project-level vs global vs personal CLAUDE.md. Shows diff preview before applying."
+triggers:
+  - "/revise-claude-md"
+  - "Update claude md"
+  - "Save learnings"
+  - "Update project instructions"
+  - "Add to CLAUDE.md"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "configuration"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# CLAUDE.md Management
+
+Capture session insights and persist them into the appropriate CLAUDE.md file.
+
+## Arguments
+
+- `/revise-claude-md` — analyze session and propose updates
+- `/revise-claude-md "specific thing"` — add a specific entry
+- `/revise-claude-md --auto` — apply without asking (for pipelines)
+
+## Workflow
+
+### Step 1: Collect Session Insights
+Analyze the current conversation for:
+- Coding patterns discovered or established
+- Project conventions learned (naming, structure, testing)
+- Build/deploy commands that work
+- Gotchas and pitfalls encountered
+- Architecture decisions made
+- Tool configurations set up
+
+### Step 2: Read Current CLAUDE.md Files
+1. Project-level: `<project-root>/CLAUDE.md`
+2. User-level: `~/.claude/CLAUDE.md`
+3. Project-specific user-level: `~/.claude/projects/<project-path>/CLAUDE.md`
+
+### Step 3: Classify Each Insight
+
+| Type | Target |
+|------|--------|
+| Project conventions, build commands | `<project>/CLAUDE.md` |
+| Global preferences, workflow rules | `~/.claude/CLAUDE.md` |
+| Project-specific personal notes | `~/.claude/projects/<path>/CLAUDE.md` |
+
+### Step 4: Propose Changes
+Present diff preview:
+```
+📝 Proposed CLAUDE.md updates:
+
+[project] CLAUDE.md:
++ ## Build Commands
++ - `npm run dev` — start dev server on port 3000
+
+[global] ~/.claude/CLAUDE.md:
++ ## Preferences
++ - Always use conventional commits
+```
+
+### Step 5: Apply (after user approval)
+1. Edit existing sections or append new sections
+2. Keep organized with clear `##` headers
+3. Avoid duplication — merge with existing
+4. Remove outdated entries if contradicted
+
+## Formatting Rules for CLAUDE.md
+
+- Use `##` headers for sections
+- Use `-` bullet lists for items
+- Keep entries concise (1 line each)
+- Group by: Commands, Conventions, Architecture, Gotchas
+- No frontmatter in CLAUDE.md files
+- CLAUDE.md should be practical — commands you run, not documentation
+
+## Rules
+
+- ALWAYS show proposed changes before applying
+- NEVER remove existing entries without explanation
+- NEVER add entries that duplicate what's already there
+- Keep CLAUDE.md files under 100 lines
+- Prefer project-level for project-specific things

package/src/gdskills/bundled/skills/platform/claude-md-management/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: claude-md-management
+description: "Use when saving session learnings, coding patterns, conventions, or commands discovered during work into CLAUDE.md files."
+triggers:
+  - "/revise-claude-md"
+  - "Update claude md"
+  - "Save learnings"
+  - "Update project instructions"
+  - "Add to CLAUDE.md"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "configuration"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# CLAUDE.md Management
+
+Capture session insights and persist them into the appropriate CLAUDE.md file.
+
+## Arguments
+
+- `/revise-claude-md` — analyze session and propose updates
+- `/revise-claude-md "specific thing"` — add a specific entry
+- `/revise-claude-md --auto` — apply without asking (for pipelines)
+
+## Workflow
+
+### Step 1: Collect Session Insights
+Analyze the current conversation for:
+- Coding patterns discovered or established
+- Project conventions learned (naming, structure, testing)
+- Build/deploy commands that work
+- Gotchas and pitfalls encountered
+- Architecture decisions made
+- Tool configurations set up
+
+### Step 2: Read Current CLAUDE.md Files
+1. Project-level: `<project-root>/CLAUDE.md`
+2. User-level: `~/.claude/CLAUDE.md`
+3. Project-specific user-level: `~/.claude/projects/<project-path>/CLAUDE.md`
+
+### Step 3: Classify Each Insight
+
+| Type | Target |
+|------|--------|
+| Project conventions, build commands | `<project>/CLAUDE.md` |
+| Global preferences, workflow rules | `~/.claude/CLAUDE.md` |
+| Project-specific personal notes | `~/.claude/projects/<path>/CLAUDE.md` |
+
+### Step 4: Propose Changes
+Present diff preview:
+```
+📝 Proposed CLAUDE.md updates:
+
+[project] CLAUDE.md:
++ ## Build Commands
++ - `npm run dev` — start dev server on port 3000
+
+[global] ~/.claude/CLAUDE.md:
++ ## Preferences
++ - Always use conventional commits
+```
+
+### Step 5: Apply (after user approval)
+1. Edit existing sections or append new sections
+2. Keep organized with clear `##` headers
+3. Avoid duplication — merge with existing
+4. Remove outdated entries if contradicted
+
+## Formatting Rules for CLAUDE.md
+
+- Use `##` headers for sections
+- Use `-` bullet lists for items
+- Keep entries concise (1 line each)
+- Group by: Commands, Conventions, Architecture, Gotchas
+- No frontmatter in CLAUDE.md files
+- CLAUDE.md should be practical — commands you run, not documentation
+
+## Rules
+
+- ALWAYS show proposed changes before applying
+- NEVER remove existing entries without explanation
+- NEVER add entries that duplicate what's already there
+- Keep CLAUDE.md files under 100 lines
+- Prefer project-level for project-specific things

package/src/gdskills/bundled/skills/platform/hookify/SKILL.codex.md

@@ -0,0 +1,100 @@
+---
+name: hookify
+description: "Create Claude Code / Cursor hooks from natural language descriptions. Generates hook config JSON for settings.json with proper event matchers and commands. Supports PreToolUse, PostToolUse, Stop, Notification events."
+triggers:
+  - "/hookify"
+  - "Create hook"
+  - "Add hook"
+  - "Run lint after edit"
+  - "Notify when done"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "configuration"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Hookify
+
+Create agent hooks from natural language descriptions.
+
+## Arguments
+
+- `/hookify <description>` — create hook from description
+- `/hookify --list` — show all current hooks
+- `/hookify --remove <event>` — remove a hook
+
+## Workflow
+
+### Step 1: Parse Request
+Understand from natural language:
+- **When**: what event triggers it (before edit, after bash, on stop)
+- **What**: what should happen (run command, check, notify)
+- **Condition**: optional matcher (specific tool, file pattern)
+
+Examples:
+- "Run lint after every file edit" → PostToolUse + Edit matcher + lint command
+- "Notify me when done" → Stop + notification command
+- "Check types before committing" → PreToolUse + Bash(git commit) + tsc
+
+### Step 2: Read Current Settings
+Check for existing hooks to avoid conflicts.
+
+### Step 3: Generate Hook Config
+
+```json
+{
+  "hooks": {
+    "<event>": [
+      {
+        "matcher": "<tool name or pattern>",
+        "command": "<shell command>",
+        "timeout": 60000
+      }
+    ]
+  }
+}
+```
+
+### Step 4: Validate
+1. Verify command exists and is executable
+2. Test standalone if safe
+3. Check for conflicts with existing hooks
+
+### Step 5: Preview & Apply
+```
+🔧 New hook:
+  Event: PostToolUse (Edit)
+  Command: npm run lint --fix
+  Timeout: 30s
+
+Add to settings.json? [confirm]
+```
+
+After confirmation, merge into settings.
+
+## Hook Event Reference
+
+| Event | When | Matcher |
+|-------|------|---------|
+| PreToolUse | Before tool runs | Tool name: Edit, Bash, Write |
+| PostToolUse | After tool runs | Tool name |
+| Notification | Agent notifies | — |
+| Stop | Response complete | — |
+| SubagentStop | Sub-agent done | — |
+
+## Common Patterns
+
+- **Auto-lint**: PostToolUse(Edit) → `eslint --fix $FILE`
+- **Auto-format**: PostToolUse(Write) → `prettier --write $FILE`
+- **Type-check gate**: PreToolUse(Bash:git commit) → `npx tsc --noEmit`
+- **Notify on done**: Stop → notification command
+
+## Rules
+
+- ALWAYS preview before applying
+- NEVER overwrite existing hooks — merge or ask
+- Keep timeouts reasonable (10-60s)
+- Warn if hook could slow down every tool call
+- Test commands before adding as hooks

package/src/gdskills/bundled/skills/platform/hookify/SKILL.cursor.md

@@ -0,0 +1,100 @@
+---
+name: hookify
+description: "Create Claude Code / Cursor hooks from natural language descriptions. Generates hook config JSON for settings.json with proper event matchers and commands. Supports PreToolUse, PostToolUse, Stop, Notification events."
+triggers:
+  - "/hookify"
+  - "Create hook"
+  - "Add hook"
+  - "Run lint after edit"
+  - "Notify when done"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "configuration"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Hookify
+
+Create agent hooks from natural language descriptions.
+
+## Arguments
+
+- `/hookify <description>` — create hook from description
+- `/hookify --list` — show all current hooks
+- `/hookify --remove <event>` — remove a hook
+
+## Workflow
+
+### Step 1: Parse Request
+Understand from natural language:
+- **When**: what event triggers it (before edit, after bash, on stop)
+- **What**: what should happen (run command, check, notify)
+- **Condition**: optional matcher (specific tool, file pattern)
+
+Examples:
+- "Run lint after every file edit" → PostToolUse + Edit matcher + lint command
+- "Notify me when done" → Stop + notification command
+- "Check types before committing" → PreToolUse + Bash(git commit) + tsc
+
+### Step 2: Read Current Settings
+Check for existing hooks to avoid conflicts.
+
+### Step 3: Generate Hook Config
+
+```json
+{
+  "hooks": {
+    "<event>": [
+      {
+        "matcher": "<tool name or pattern>",
+        "command": "<shell command>",
+        "timeout": 60000
+      }
+    ]
+  }
+}
+```
+
+### Step 4: Validate
+1. Verify command exists and is executable
+2. Test standalone if safe
+3. Check for conflicts with existing hooks
+
+### Step 5: Preview & Apply
+```
+🔧 New hook:
+  Event: PostToolUse (Edit)
+  Command: npm run lint --fix
+  Timeout: 30s
+
+Add to settings.json? [confirm]
+```
+
+After confirmation, merge into settings.
+
+## Hook Event Reference
+
+| Event | When | Matcher |
+|-------|------|---------|
+| PreToolUse | Before tool runs | Tool name: Edit, Bash, Write |
+| PostToolUse | After tool runs | Tool name |
+| Notification | Agent notifies | — |
+| Stop | Response complete | — |
+| SubagentStop | Sub-agent done | — |
+
+## Common Patterns
+
+- **Auto-lint**: PostToolUse(Edit) → `eslint --fix $FILE`
+- **Auto-format**: PostToolUse(Write) → `prettier --write $FILE`
+- **Type-check gate**: PreToolUse(Bash:git commit) → `npx tsc --noEmit`
+- **Notify on done**: Stop → notification command
+
+## Rules
+
+- ALWAYS preview before applying
+- NEVER overwrite existing hooks — merge or ask
+- Keep timeouts reasonable (10-60s)
+- Warn if hook could slow down every tool call
+- Test commands before adding as hooks

package/src/gdskills/bundled/skills/platform/hookify/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: hookify
+description: "Use when adding automated hook behavior to Claude Code or Cursor from a natural language description."
+triggers:
+  - "/hookify"
+  - "Create hook"
+  - "Add hook"
+  - "Run lint after edit"
+  - "Notify when done"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "configuration"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Hookify
+
+Create agent hooks from natural language descriptions.
+
+## Arguments
+
+- `/hookify <description>` — create hook from description
+- `/hookify --list` — show all current hooks
+- `/hookify --remove <event>` — remove a hook
+
+## Workflow
+
+### Step 1: Parse Request
+Understand from natural language:
+- **When**: what event triggers it (before edit, after bash, on stop)
+- **What**: what should happen (run command, check, notify)
+- **Condition**: optional matcher (specific tool, file pattern)
+
+Examples:
+- "Run lint after every file edit" → PostToolUse + Edit matcher + lint command
+- "Notify me when done" → Stop + notification command
+- "Check types before committing" → PreToolUse + Bash(git commit) + tsc
+
+### Step 2: Read Current Settings
+Check for existing hooks to avoid conflicts.
+
+### Step 3: Generate Hook Config
+
+```json
+{
+  "hooks": {
+    "<event>": [
+      {
+        "matcher": "<tool name or pattern>",
+        "command": "<shell command>",
+        "timeout": 60000
+      }
+    ]
+  }
+}
+```
+
+### Step 4: Validate
+1. Verify command exists and is executable
+2. Test standalone if safe
+3. Check for conflicts with existing hooks
+
+### Step 5: Preview & Apply
+```
+🔧 New hook:
+  Event: PostToolUse (Edit)
+  Command: npm run lint --fix
+  Timeout: 30s
+
+Add to settings.json? [confirm]
+```
+
+After confirmation, merge into settings.
+
+## Hook Event Reference
+
+| Event | When | Matcher |
+|-------|------|---------|
+| PreToolUse | Before tool runs | Tool name: Edit, Bash, Write |
+| PostToolUse | After tool runs | Tool name |
+| Notification | Agent notifies | — |
+| Stop | Response complete | — |
+| SubagentStop | Sub-agent done | — |
+
+## Common Patterns
+
+- **Auto-lint**: PostToolUse(Edit) → `eslint --fix $FILE`
+- **Auto-format**: PostToolUse(Write) → `prettier --write $FILE`
+- **Type-check gate**: PreToolUse(Bash:git commit) → `npx tsc --noEmit`
+- **Notify on done**: Stop → notification command
+
+## Rules
+
+- ALWAYS preview before applying
+- NEVER overwrite existing hooks — merge or ask
+- Keep timeouts reasonable (10-60s)
+- Warn if hook could slow down every tool call
+- Test commands before adding as hooks

package/src/gdskills/bundled/skills/quality/changelog/SKILL.claude.md

@@ -0,0 +1,45 @@
+---
+description: Generate changelog from commits between tags or releases
+allowed-tools: Bash(git log:*), Bash(git tag:*), Bash(git describe:*), Bash(git rev-list:*)
+---
+
+## Context
+
+- All tags (latest first): !`git tag --sort=-creatordate | head -20`
+- Commits since last tag: !`git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline 2>/dev/null | head -50`
+- Current branch: !`git branch --show-current`
+
+## Your task
+
+Generate changelog for: $ARGUMENTS
+
+- No args → last tag to HEAD
+- One arg (tag) → that tag to HEAD
+- Two args (e.g. `v1.0.0 v1.1.0`) → between those tags
+
+### Steps
+
+1. Determine commit range from arguments
+2. Get full log: `git log <from>..<to> --pretty=format:"%h %s (%an)" --no-merges`
+3. Categorize by conventional commit prefix:
+   - `feat:` → **Features**
+   - `fix:` → **Bug Fixes**
+   - `perf:` → **Performance**
+   - `refactor:` → **Refactoring**
+   - `docs:` → **Documentation**
+   - `chore:` / `build:` / `ci:` → **Maintenance**
+   - `test:` → **Tests**
+   - uncategorized → **Other Changes**
+
+4. Output:
+```markdown
+## [version] — YYYY-MM-DD
+
+### Features
+- Description (abc1234)
+
+### Bug Fixes
+- Description (abc1234)
+```
+
+5. Also output compact version for `gh release create --notes`

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

@@ -0,0 +1,84 @@
+---
+name: changelog
+description: "Generate changelog from git commits between tags or date ranges. Groups by conventional commit type (features, fixes, performance, etc.), links PRs and issues. Supports output to file or prepend to existing CHANGELOG.md."
+triggers:
+  - "/changelog"
+  - "Generate changelog"
+  - "What changed since"
+  - "Release notes"
+  - "What's new"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Changelog Generator
+
+Generate structured changelog from git history.
+
+## Arguments
+
+- `/changelog` — latest tag to HEAD
+- `/changelog v1.0..v2.0` — between tags
+- `/changelog --since 2024-01-01` — since date
+- `/changelog --output <file>` — write to file
+- `/changelog --prepend` — prepend to existing CHANGELOG.md
+- `/changelog --format compact` — one-liner per change
+
+## Workflow
+
+### Step 1: Determine Range
+1. `git tag --sort=-version:refname` — list recent tags
+2. Default: from latest tag to HEAD
+3. Between tags or since date if specified
+
+### Step 2: Collect Commits
+```bash
+git log <range> --pretty=format:"%H|%s|%an|%ad" --date=short
+```
+
+### Step 3: Parse & Classify
+
+| Prefix | Section |
+|--------|---------|
+| feat: | Features |
+| fix: | Bug Fixes |
+| perf: | Performance |
+| refactor: | Refactoring |
+| docs: | Documentation |
+| test: | Tests |
+| chore: | Maintenance |
+| BREAKING CHANGE | Breaking Changes |
+
+Extract scope, PR references `(#123)`, issue references `fixes #456`.
+
+### Step 4: Enrich (optional)
+If `gh` CLI available: fetch PR titles for merge commits, get authors and labels.
+
+### Step 5: Generate Output
+
+```markdown
+# Changelog
+
+## [v1.3.0] - 2024-03-15
+
+### Breaking Changes
+- **auth**: Remove deprecated OAuth1 support (#234)
+
+### Features
+- **api**: Add batch processing endpoint (#220)
+
+### Bug Fixes
+- **db**: Fix connection pool leak under load (#228)
+```
+
+## Rules
+
+- Deduplicate identical commit messages
+- Skip merge commits (use PR title instead)
+- If no conventional commits found, fall back to plain list by date
+- Breaking changes always go first
+- One line per change