@mrciphersmith/keryx 0.2.9

package/src/gdskills/bundled/skills/quality/changelog/SKILL.cursor.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

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

@@ -0,0 +1,84 @@
+---
+name: changelog
+description: "Use when generating a changelog, release notes, or summarizing what changed between tags, versions, or date ranges."
+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

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

@@ -0,0 +1,66 @@
+---
+name: commit
+description: "Smart git commit: auto-stages changes, analyzes diff, generates conventional commit message. Supports custom messages, amend, and selective staging. Use when committing code changes with meaningful messages."
+triggers:
+  - "/commit"
+  - "Commit changes"
+  - "Commit this"
+  - "Save changes"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Smart Commit
+
+Create well-structured git commits from current changes.
+
+## Workflow
+
+### Phase 1: Analyze Changes
+1. Run `git status` and `git diff --staged` and `git diff` to understand all changes
+2. Run `git log --oneline -5` to match the repo's commit message style
+3. Check for conventional commit patterns in history
+
+### Phase 2: Stage Files
+If nothing is staged, intelligently stage relevant files:
+- Stage modified and new files that are part of the logical change
+- **NEVER** stage `.env`, credentials, secrets, or large binary files
+- Prefer `git add <specific files>` over `git add -A`
+- Ask the user before staging untracked files that look unrelated to recent work
+
+### Phase 3: Generate Commit Message
+Analyze the diff and generate a concise commit message:
+- First line: `<type>(<scope>): <description>` (under 72 chars)
+- Types: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, `style:`, `perf:`
+- Optional body: explain "why" not "what" (the diff shows "what")
+- **NEVER** add "Co-Authored-By" or any co-authorship lines
+
+### Phase 4: Commit
+Create the commit using heredoc format:
+```bash
+git commit -m "$(cat <<'EOF'
+type(scope): description
+EOF
+)"
+```
+
+### Phase 5: Verify
+Show the result: `git log --oneline -1` and `git status`
+
+## Arguments
+
+- `/commit` — auto-generate message from diff
+- `/commit <message>` — use provided message as-is
+- `/commit --amend` — amend the last commit (only when explicitly requested)
+- `/commit -a` — stage all modified files before committing
+
+## Rules
+
+- NEVER use `--no-verify` or skip hooks
+- NEVER add Co-Authored-By lines
+- If pre-commit hook fails: fix the issue, re-stage, create a NEW commit (don't amend)
+- Follow existing commit message conventions in the repository

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

@@ -0,0 +1,66 @@
+---
+name: commit
+description: "Smart git commit: auto-stages changes, analyzes diff, generates conventional commit message. Supports custom messages, amend, and selective staging. Use when committing code changes with meaningful messages."
+triggers:
+  - "/commit"
+  - "Commit changes"
+  - "Commit this"
+  - "Save changes"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Smart Commit
+
+Create well-structured git commits from current changes.
+
+## Workflow
+
+### Phase 1: Analyze Changes
+1. Run `git status` and `git diff --staged` and `git diff` to understand all changes
+2. Run `git log --oneline -5` to match the repo's commit message style
+3. Check for conventional commit patterns in history
+
+### Phase 2: Stage Files
+If nothing is staged, intelligently stage relevant files:
+- Stage modified and new files that are part of the logical change
+- **NEVER** stage `.env`, credentials, secrets, or large binary files
+- Prefer `git add <specific files>` over `git add -A`
+- Ask the user before staging untracked files that look unrelated to recent work
+
+### Phase 3: Generate Commit Message
+Analyze the diff and generate a concise commit message:
+- First line: `<type>(<scope>): <description>` (under 72 chars)
+- Types: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, `style:`, `perf:`
+- Optional body: explain "why" not "what" (the diff shows "what")
+- **NEVER** add "Co-Authored-By" or any co-authorship lines
+
+### Phase 4: Commit
+Create the commit using heredoc format:
+```bash
+git commit -m "$(cat <<'EOF'
+type(scope): description
+EOF
+)"
+```
+
+### Phase 5: Verify
+Show the result: `git log --oneline -1` and `git status`
+
+## Arguments
+
+- `/commit` — auto-generate message from diff
+- `/commit <message>` — use provided message as-is
+- `/commit --amend` — amend the last commit (only when explicitly requested)
+- `/commit -a` — stage all modified files before committing
+
+## Rules
+
+- NEVER use `--no-verify` or skip hooks
+- NEVER add Co-Authored-By lines
+- If pre-commit hook fails: fix the issue, re-stage, create a NEW commit (don't amend)
+- Follow existing commit message conventions in the repository

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

@@ -0,0 +1,66 @@
+---
+name: commit
+description: "Use when committing code changes and a well-structured conventional commit message is needed, with optional amend or selective staging."
+triggers:
+  - "/commit"
+  - "Commit changes"
+  - "Commit this"
+  - "Save changes"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "workflow"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Smart Commit
+
+Create well-structured git commits from current changes.
+
+## Workflow
+
+### Phase 1: Analyze Changes
+1. Run `git status` and `git diff --staged` and `git diff` to understand all changes
+2. Run `git log --oneline -5` to match the repo's commit message style
+3. Check for conventional commit patterns in history
+
+### Phase 2: Stage Files
+If nothing is staged, intelligently stage relevant files:
+- Stage modified and new files that are part of the logical change
+- **NEVER** stage `.env`, credentials, secrets, or large binary files
+- Prefer `git add <specific files>` over `git add -A`
+- Ask the user before staging untracked files that look unrelated to recent work
+
+### Phase 3: Generate Commit Message
+Analyze the diff and generate a concise commit message:
+- First line: `<type>(<scope>): <description>` (under 72 chars)
+- Types: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, `style:`, `perf:`
+- Optional body: explain "why" not "what" (the diff shows "what")
+- **NEVER** add "Co-Authored-By" or any co-authorship lines
+
+### Phase 4: Commit
+Create the commit using heredoc format:
+```bash
+git commit -m "$(cat <<'EOF'
+type(scope): description
+EOF
+)"
+```
+
+### Phase 5: Verify
+Show the result: `git log --oneline -1` and `git status`
+
+## Arguments
+
+- `/commit` — auto-generate message from diff
+- `/commit <message>` — use provided message as-is
+- `/commit --amend` — amend the last commit (only when explicitly requested)
+- `/commit -a` — stage all modified files before committing
+
+## Rules
+
+- NEVER use `--no-verify` or skip hooks
+- NEVER add Co-Authored-By lines
+- If pre-commit hook fails: fix the issue, re-stage, create a NEW commit (don't amend)
+- Follow existing commit message conventions in the repository

package/src/gdskills/bundled/skills/quality/db-migrate/SKILL.claude.md

@@ -0,0 +1,40 @@
+---
+description: Create and apply database migrations (Drizzle, Prisma, Knex, raw SQL)
+allowed-tools: Bash(*), Read(*), Write(*), Glob(*)
+---
+
+## Context
+
+- Migration tool: !`ls drizzle.config.* knexfile.* prisma/schema.prisma 2>/dev/null | head -3 || echo "none found"`
+- Existing migrations: !`ls migrations/ db/migrations/ prisma/migrations/ 2>/dev/null | tail -10 || echo "none"`
+- DB env: !`grep -E "DATABASE_URL|DB_HOST|POSTGRES" .env 2>/dev/null | sed 's/=.*/=***/' || echo "no .env"`
+- Migration scripts: !`cat package.json 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); [print(k+':',v) for k,v in d.get('scripts',{}).items() if any(x in k for x in ['migrat','drizzle','prisma'])]" 2>/dev/null || echo "none"`
+
+## Your task
+
+Action: $ARGUMENTS (e.g. `create add_user_sessions_table`, `apply`, `status`, `rollback`)
+
+### Detect tool
+- `drizzle.config.*` → Drizzle ORM
+- `prisma/schema.prisma` → Prisma
+- `knexfile.*` → Knex
+- `migrations/*.sql` → Raw SQL
+
+### `create <name>`
+- Drizzle: `bunx drizzle-kit generate`
+- Prisma: `bunx prisma migrate dev --name <name>`
+- Knex: `npx knex migrate:make <name>`
+- Raw SQL: create `migrations/YYYYMMDD_HHMMSS_<name>.sql` with UP/DOWN, scaffold SQL from name
+
+### `apply` / empty
+- Drizzle: `bunx drizzle-kit migrate`
+- Prisma: `bunx prisma migrate deploy`
+- Knex: `npx knex migrate:latest`
+
+### `status`
+Show applied vs pending
+
+### `rollback`
+Roll back last migration
+
+Always show SQL before running, confirm success after.

package/src/gdskills/bundled/skills/quality/db-migrate/SKILL.codex.md

@@ -0,0 +1,66 @@
+---
+name: db-migrate
+description: "Database migration management: create, apply, rollback, check status. Auto-detects Prisma, TypeORM, Knex, Sequelize, Drizzle, Alembic, raw SQL. Shows migration SQL preview before applying."
+triggers:
+  - "/db-migrate"
+  - "Create migration"
+  - "Run migrations"
+  - "Migration status"
+  - "Rollback migration"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "database"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Database Migration
+
+Create, apply, and manage database migrations.
+
+## Arguments
+
+- `/db-migrate create <name>` — create new migration
+- `/db-migrate apply` — apply pending migrations
+- `/db-migrate status` — show migration status
+- `/db-migrate rollback` — rollback last migration
+
+## Workflow
+
+### Step 1: Detect ORM/Migration Tool
+Search for: `prisma/schema.prisma`, `ormconfig.*`, `data-source.ts`, `knexfile.*`, `.sequelizerc`, `drizzle.config.ts`, `alembic.ini`, `migrations/` with raw SQL.
+
+### Step 2: Execute Command
+
+**Create:**
+
+| Tool | Command |
+|------|---------|
+| Prisma | `npx prisma migrate dev --name <name>` |
+| TypeORM | `npx typeorm migration:generate -n <name>` |
+| Knex | `npx knex migrate:make <name>` |
+| Sequelize | `npx sequelize-cli migration:generate --name <name>` |
+| Drizzle | `npx drizzle-kit generate:migration --name <name>` |
+| Alembic | `alembic revision --autogenerate -m "<name>"` |
+
+**Apply / Status / Rollback** — analogous commands per tool.
+
+### Step 3: If Creating — Help Write Migration
+1. Ask what schema changes are needed (or infer from context)
+2. For schema-based ORMs — edit schema first, then generate
+3. For code-based migrations — generate template and fill in up/down
+4. Review generated migration before applying
+
+### Step 4: Apply & Verify
+1. Show migration SQL preview if possible
+2. Apply migration
+3. Verify with status command
+
+## Rules
+
+- ALWAYS show migration content before applying in production
+- ALWAYS confirm before rollback operations
+- NEVER apply to production without explicit confirmation
+- For destructive operations (drop table, remove column), double-warn
+- If ORM can't be detected, ask the user

package/src/gdskills/bundled/skills/quality/db-migrate/SKILL.cursor.md

@@ -0,0 +1,66 @@
+---
+name: db-migrate
+description: "Database migration management: create, apply, rollback, check status. Auto-detects Prisma, TypeORM, Knex, Sequelize, Drizzle, Alembic, raw SQL. Shows migration SQL preview before applying."
+triggers:
+  - "/db-migrate"
+  - "Create migration"
+  - "Run migrations"
+  - "Migration status"
+  - "Rollback migration"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "database"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Database Migration
+
+Create, apply, and manage database migrations.
+
+## Arguments
+
+- `/db-migrate create <name>` — create new migration
+- `/db-migrate apply` — apply pending migrations
+- `/db-migrate status` — show migration status
+- `/db-migrate rollback` — rollback last migration
+
+## Workflow
+
+### Step 1: Detect ORM/Migration Tool
+Search for: `prisma/schema.prisma`, `ormconfig.*`, `data-source.ts`, `knexfile.*`, `.sequelizerc`, `drizzle.config.ts`, `alembic.ini`, `migrations/` with raw SQL.
+
+### Step 2: Execute Command
+
+**Create:**
+
+| Tool | Command |
+|------|---------|
+| Prisma | `npx prisma migrate dev --name <name>` |
+| TypeORM | `npx typeorm migration:generate -n <name>` |
+| Knex | `npx knex migrate:make <name>` |
+| Sequelize | `npx sequelize-cli migration:generate --name <name>` |
+| Drizzle | `npx drizzle-kit generate:migration --name <name>` |
+| Alembic | `alembic revision --autogenerate -m "<name>"` |
+
+**Apply / Status / Rollback** — analogous commands per tool.
+
+### Step 3: If Creating — Help Write Migration
+1. Ask what schema changes are needed (or infer from context)
+2. For schema-based ORMs — edit schema first, then generate
+3. For code-based migrations — generate template and fill in up/down
+4. Review generated migration before applying
+
+### Step 4: Apply & Verify
+1. Show migration SQL preview if possible
+2. Apply migration
+3. Verify with status command
+
+## Rules
+
+- ALWAYS show migration content before applying in production
+- ALWAYS confirm before rollback operations
+- NEVER apply to production without explicit confirmation
+- For destructive operations (drop table, remove column), double-warn
+- If ORM can't be detected, ask the user

package/src/gdskills/bundled/skills/quality/db-migrate/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: db-migrate
+description: "Use when creating, applying, rolling back, or checking the status of database migrations."
+triggers:
+  - "/db-migrate"
+  - "Create migration"
+  - "Run migrations"
+  - "Migration status"
+  - "Rollback migration"
+metadata:
+  author: "MrCipherSmith"
+  version: "1.0.0"
+  category: "database"
+license: "MIT"
+compatibility: "cursor,codex,zed,opencode,claude"
+---
+
+# Database Migration
+
+Create, apply, and manage database migrations.
+
+## Arguments
+
+- `/db-migrate create <name>` — create new migration
+- `/db-migrate apply` — apply pending migrations
+- `/db-migrate status` — show migration status
+- `/db-migrate rollback` — rollback last migration
+
+## Workflow
+
+### Step 1: Detect ORM/Migration Tool
+Search for: `prisma/schema.prisma`, `ormconfig.*`, `data-source.ts`, `knexfile.*`, `.sequelizerc`, `drizzle.config.ts`, `alembic.ini`, `migrations/` with raw SQL.
+
+### Step 2: Execute Command
+
+**Create:**
+
+| Tool | Command |
+|------|---------|
+| Prisma | `npx prisma migrate dev --name <name>` |
+| TypeORM | `npx typeorm migration:generate -n <name>` |
+| Knex | `npx knex migrate:make <name>` |
+| Sequelize | `npx sequelize-cli migration:generate --name <name>` |
+| Drizzle | `npx drizzle-kit generate:migration --name <name>` |
+| Alembic | `alembic revision --autogenerate -m "<name>"` |
+
+**Apply / Status / Rollback** — analogous commands per tool.
+
+### Step 3: If Creating — Help Write Migration
+1. Ask what schema changes are needed (or infer from context)
+2. For schema-based ORMs — edit schema first, then generate
+3. For code-based migrations — generate template and fill in up/down
+4. Review generated migration before applying
+
+### Step 4: Apply & Verify
+1. Show migration SQL preview if possible
+2. Apply migration
+3. Verify with status command
+
+## Rules
+
+- ALWAYS show migration content before applying in production
+- ALWAYS confirm before rollback operations
+- NEVER apply to production without explicit confirmation
+- For destructive operations (drop table, remove column), double-warn
+- If ORM can't be detected, ask the user

package/src/gdskills/bundled/skills/quality/dependency-update/SKILL.claude.md

@@ -0,0 +1,45 @@
+---
+description: Update dependencies with compatibility checks and test verification
+allowed-tools: Bash(*), Read(*), Edit(*), Write(*)
+---
+
+## Context
+
+- Package manager: !`ls bun.lockb 2>/dev/null && echo "bun" || ls yarn.lock 2>/dev/null && echo "yarn" || echo "npm"`
+- Outdated packages: !`bun outdated 2>/dev/null || npm outdated 2>/dev/null | head -30`
+- Test script: !`cat package.json 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('scripts',{}).get('test','none'))" 2>/dev/null`
+
+## Your task
+
+Update dependencies: $ARGUMENTS (empty = all outdated)
+
+### Steps
+
+1. **Snapshot**: `cp package.json package.json.backup`
+
+2. **Categorize** updates: patch / minor (auto) vs major (manual analysis)
+
+3. **Apply patch + minor**:
+```bash
+bun update 2>/dev/null || npx npm-check-updates -u --target minor && npm install
+```
+
+4. **Run tests**:
+```bash
+bun test 2>/dev/null || npm test 2>/dev/null
+```
+If fail → identify breaking update → rollback that package
+
+5. **For major updates** (if in args or --major flag):
+   - Check CHANGELOG/GitHub releases for breaking changes
+   - Report: what needs updating in codebase
+   - Apply only if no breaking changes affect this project
+
+6. **Always update** packages with known CVEs regardless of version jump
+
+7. **Restore on failure**: `cp package.json.backup package.json && bun install`
+
+### Final report
+- Updated: old → new versions
+- Skipped: package + reason
+- Manual action: major changes requiring code updates