genskills 1.0.0

package/skills/documentation/doc-gen/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: genskills:doc-gen
+description: >
+  Generate documentation for code — inline comments, JSDoc/docstrings, module docs.
+  Triggers on: "document this", "add docs", "generate documentation",
+  "add comments", "write docstrings".
+user-invocable: true
+argument-hint: "[file or directory to document]"
+allowed-tools: "Read, Edit, Grep, Glob"
+genskills-version: "1.0.0"
+genskills-category: "documentation"
+genskills-depends: []
+---
+
+# Documentation Generator
+
+Generate inline documentation for code.
+
+## Process
+
+### Step 1: Analyze Target
+- Read the file(s) specified in `$ARGUMENTS`
+- Detect the language and documentation convention:
+  - TypeScript/JavaScript → JSDoc (`/** */`)
+  - Python → Docstrings (Google, NumPy, or Sphinx style)
+  - Go → GoDoc comments
+  - Rust → `///` doc comments
+  - Java/Kotlin → Javadoc
+
+### Step 2: Identify What Needs Documentation
+- Exported/public functions and classes
+- Complex private functions
+- Type definitions and interfaces
+- Module-level documentation
+- Configuration constants
+
+### Step 3: Generate Documentation
+For each function/class/type:
+- **Description**: What it does (not how)
+- **Parameters**: Name, type, description, default values
+- **Returns**: Type and description
+- **Throws/Raises**: Error conditions
+- **Examples**: Usage examples for complex APIs
+- **Deprecation**: Notes if applicable
+
+### Step 4: Apply
+- Add documentation comments using the Edit tool
+- Preserve existing documentation — only add where missing
+- Follow the project's existing documentation style

package/skills/documentation/readme-gen/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: genskills:readme-gen
+description: >
+  Generate or update a comprehensive README.md for the project.
+  Triggers on: "generate README", "create README", "update README",
+  "write README", "project README".
+user-invocable: true
+argument-hint: "[style: minimal|standard|detailed]"
+allowed-tools: "Read, Write, Edit, Grep, Glob, Bash(git remote*)"
+genskills-version: "1.0.0"
+genskills-category: "documentation"
+genskills-depends: []
+---
+
+# README Generator
+
+Generate a comprehensive project README.
+
+## Process
+
+### Step 1: Analyze Project
+- Read `package.json`, `pyproject.toml`, `Cargo.toml`, etc. for project metadata
+- Identify the tech stack from files and dependencies
+- Check for existing README.md to preserve user content
+- Read the project structure for architecture overview
+
+### Step 2: Determine Style
+From `$ARGUMENTS` (default: "standard"):
+- **minimal**: Name, description, install, usage
+- **standard**: Full README with all sections
+- **detailed**: Comprehensive with architecture, contributing guidelines
+
+### Step 3: Generate README
+```markdown
+# Project Name
+
+Brief description of what this project does.
+
+## Features
+- Key feature 1
+- Key feature 2
+
+## Prerequisites
+- Required tools and versions
+
+## Installation
+Step-by-step installation instructions
+
+## Usage
+Code examples and CLI usage
+
+## Configuration
+Environment variables and config files
+
+## Project Structure
+Key directories and their purposes
+
+## Contributing
+How to contribute (if detailed style)
+
+## License
+License information
+```
+
+### Step 4: Write
+- If README.md exists, show a diff of proposed changes
+- If new, create the file
+- Preserve any existing badges, custom sections, or user-written content

package/skills/project-management/changelog-gen/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: genskills:changelog-gen
+description: >
+  Generate and maintain a CHANGELOG.md from git history, following Keep a Changelog format.
+  Triggers on: "generate changelog", "update changelog", "what changed", "changelog".
+user-invocable: true
+argument-hint: "[version number or 'unreleased']"
+allowed-tools: "Read, Write, Edit, Bash(git log*), Bash(git tag*)"
+genskills-version: "1.0.0"
+genskills-category: "project-management"
+genskills-depends:
+  - genskills:git-commit
+---
+
+# Changelog Generator
+
+Generate and maintain a changelog from git history.
+
+## Process
+
+### Step 1: Analyze Git History
+- Get the last tag: `git describe --tags --abbrev=0` (or use all history if no tags)
+- Get commits since last tag: `git log <last-tag>..HEAD --oneline`
+- Parse commit messages for conventional commit types
+
+### Step 2: Categorize Changes
+Group commits into Keep a Changelog categories:
+- **Added**: New features (`feat:`)
+- **Changed**: Changes to existing features
+- **Deprecated**: Features marked for removal
+- **Removed**: Removed features
+- **Fixed**: Bug fixes (`fix:`)
+- **Security**: Security-related changes
+
+### Step 3: Generate/Update CHANGELOG.md
+If `$ARGUMENTS` provides a version number, create a release entry.
+Otherwise, update the `[Unreleased]` section.
+
+Format:
+```markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [Unreleased]
+
+### Added
+- Feature description (#PR)
+
+### Fixed
+- Bug fix description (#PR)
+
+## [1.0.0] - 2026-03-23
+
+### Added
+- Initial release features
+```
+
+### Step 4: Verify
+- Show the generated/updated changelog section
+- Suggest committing the changelog update

package/skills/project-management/release-notes/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: genskills:release-notes
+description: >
+  Generate polished release notes for a version, suitable for GitHub Releases
+  or user-facing announcements. Triggers on: "release notes", "write release",
+  "create release", "publish release".
+user-invocable: true
+argument-hint: "[version tag, e.g. v1.2.0]"
+allowed-tools: "Read, Grep, Bash(git log*), Bash(git tag*), Bash(gh release*)"
+genskills-version: "1.0.0"
+genskills-category: "project-management"
+genskills-depends:
+  - genskills:changelog-gen
+---
+
+# Release Notes
+
+Generate polished release notes for public consumption.
+
+## Process
+
+### Step 1: Determine Version
+- Use `$ARGUMENTS` as the version tag
+- If not provided, suggest based on changes (semver):
+  - Breaking changes → major bump
+  - New features → minor bump
+  - Bug fixes only → patch bump
+
+### Step 2: Gather Changes
+- Get commits between previous tag and HEAD
+- Read CHANGELOG.md if it exists
+- Check for PRs merged: `gh pr list --state merged --base main`
+
+### Step 3: Write Release Notes
+Create user-friendly release notes:
+
+```markdown
+# Release v1.2.0
+
+## Highlights
+<1-2 sentence summary of the most impactful changes>
+
+## What's New
+- Feature 1: brief description
+- Feature 2: brief description
+
+## Bug Fixes
+- Fixed: issue description
+
+## Breaking Changes
+- Description of what changed and migration steps
+
+## Contributors
+- @username — contribution description
+
+**Full Changelog**: v1.1.0...v1.2.0
+```
+
+### Step 4: Publish (optional)
+- If user confirms, create a GitHub release:
+  `gh release create <tag> --title "..." --notes "..."`
+- Attach build artifacts if available

package/skills/project-management/task-tracker/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: genskills:task-tracker
+description: >
+  Track and manage project tasks, create TODO lists, and organize work items.
+  Triggers on: "track tasks", "create task", "list tasks", "what's left to do",
+  "project status", "task list".
+user-invocable: true
+argument-hint: "[action: list|add|done|status]"
+allowed-tools: "Read, Write, Edit, Grep, Glob, Bash(git log*)"
+genskills-version: "1.0.0"
+genskills-category: "project-management"
+genskills-depends: []
+---
+
+# Task Tracker
+
+Manage project tasks and track progress.
+
+## Actions
+
+### List (`$0` = "list" or default)
+- Search for TODO/FIXME/HACK/XXX comments across the codebase
+- Check for existing task files: `TODO.md`, `TASKS.md`, issues
+- Group by priority (critical, high, medium, low)
+- Group by area (frontend, backend, infra, docs)
+
+### Add (`$0` = "add")
+- Add a task to the project's task tracking file
+- If no task file exists, create `TODO.md` at project root
+- Format: `- [ ] [priority] description (added: date)`
+
+### Done (`$0` = "done")
+- Mark a task as completed
+- Update the task file with completion date
+- Remove the corresponding TODO comment from code if applicable
+
+### Status (`$0` = "status")
+- Show overall project status:
+  - Total tasks: open vs completed
+  - Recent git activity: `git log --oneline -10`
+  - Open TODO/FIXME count by file
+  - Upcoming deadlines if any are noted in task files

package/skills/workflow/branch-manager/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: genskills:branch-manager
+description: >
+  Manage git branches — create, switch, merge, rebase, clean up stale branches.
+  Triggers on: "manage branches", "clean branches", "create branch",
+  "merge branch", "rebase", "branch cleanup".
+user-invocable: true
+argument-hint: "[action: create|cleanup|merge|rebase] [branch name]"
+allowed-tools: "Bash(git *), Read"
+genskills-version: "1.0.0"
+genskills-category: "workflow"
+genskills-depends: []
+---
+
+# Branch Manager
+
+Manage git branches efficiently.
+
+## Actions
+
+### Create (`$0` = "create")
+- Create a new branch from the current or specified base
+- Use naming convention: `<type>/<short-description>`
+- Types: feature/, fix/, chore/, docs/, refactor/
+- Example: `feature/add-user-auth`
+- Switch to the new branch
+
+### Cleanup (`$0` = "cleanup")
+- List all local branches
+- Identify merged branches: `git branch --merged main`
+- Identify stale branches (no commits in 30+ days)
+- Show branches with their last commit date
+- Confirm before deleting — never force delete without asking
+- Clean up remote tracking: `git remote prune origin`
+
+### Merge (`$0` = "merge")
+- Merge `$1` into the current branch
+- If conflicts arise, show the conflicting files and help resolve
+- Never use `--force` or destructive operations without explicit confirmation
+
+### Rebase (`$0` = "rebase")
+- Rebase current branch onto `$1` (defaults to main)
+- If conflicts arise, help resolve them step by step
+- Warn about rebase implications for shared branches
+
+### Status (default if no action specified)
+- Show current branch
+- Show `git log --oneline -10`
+- Show branches with tracking status
+- Show uncommitted changes summary

package/skills/workflow/ci-fix/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: genskills:ci-fix
+description: >
+  Diagnose and fix failing CI/CD pipeline issues. Analyzes build logs,
+  test failures, and configuration problems. Triggers on: "fix CI", "CI failing",
+  "pipeline broken", "build failed", "GitHub Actions failing".
+user-invocable: true
+argument-hint: "[CI run URL or 'latest']"
+allowed-tools: "Read, Edit, Grep, Glob, Bash(gh *), Bash(git *)"
+genskills-version: "1.0.0"
+genskills-category: "workflow"
+genskills-depends: []
+---
+
+# CI Fix
+
+Diagnose and fix CI/CD pipeline failures.
+
+## Process
+
+### Step 1: Get CI Logs
+- If `$ARGUMENTS` contains a URL, fetch that run's logs
+- If `$ARGUMENTS` = "latest" or empty, get the latest run:
+  `gh run list --limit 5` then `gh run view <id> --log-failed`
+- Identify the failing step and error messages
+
+### Step 2: Diagnose
+Common failure categories:
+- **Test failures**: Read failing test, identify the root cause
+- **Build errors**: TypeScript errors, missing dependencies, syntax issues
+- **Lint failures**: Style violations, import errors
+- **Dependency issues**: Lock file conflicts, missing packages, version incompatibilities
+- **Environment issues**: Missing env vars, wrong Node/Python version
+- **Timeout**: Slow tests, infinite loops, missing mocks
+
+### Step 3: Fix
+- Apply the fix to the relevant files
+- If it's a flaky test, add retry logic or fix the underlying race condition
+- If it's a config issue, update the workflow file
+- If it's a dependency issue, update package.json / requirements.txt
+
+### Step 4: Verify Locally
+- Run the failing command locally to verify the fix
+- Suggest pushing the fix and monitoring the CI run

package/skills/workflow/deploy/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: genskills:deploy
+description: >
+  Guide deployment workflows with pre-deploy checks, build verification,
+  and post-deploy monitoring. Triggers on: "deploy", "release to production",
+  "ship it", "push to prod".
+user-invocable: true
+disable-model-invocation: true
+argument-hint: "[environment: staging|production]"
+allowed-tools: "Read, Grep, Glob, Bash"
+genskills-version: "1.0.0"
+genskills-category: "workflow"
+genskills-depends: []
+---
+
+# Deploy
+
+Guided deployment workflow with safety checks.
+
+**Note**: This skill is user-invocable only (not auto-triggered) for safety.
+
+## Process
+
+### Step 1: Pre-deploy Checklist
+- [ ] All tests passing
+- [ ] No uncommitted changes (`git status`)
+- [ ] On the correct branch
+- [ ] Branch is up to date with remote
+- [ ] No pending dependency vulnerabilities (`npm audit` / `pip audit`)
+- [ ] Build succeeds locally
+
+### Step 2: Identify Deploy Method
+Check the project for:
+- `Dockerfile` / `docker-compose.yml` → Docker-based
+- `vercel.json` / `.vercel/` → Vercel
+- `netlify.toml` → Netlify
+- `.github/workflows/deploy*` → GitHub Actions
+- `fly.toml` → Fly.io
+- `Procfile` → Heroku
+- Custom scripts in `package.json` (`deploy`, `release`)
+
+### Step 3: Execute Deploy
+Based on detected method, run the appropriate deploy command.
+Always confirm with the user before executing deployment commands.
+
+Environment from `$ARGUMENTS`:
+- `staging` (default): Deploy to staging/preview
+- `production`: Deploy to production (requires explicit confirmation)
+
+### Step 4: Post-deploy
+- Verify the deployment succeeded
+- Show the deployed URL if available
+- Suggest monitoring steps

package/skills/workflow/git-commit/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: genskills:git-commit
+description: >
+  Create well-structured git commits with conventional commit format,
+  smart staging, and AI-generated messages. Triggers on: "commit",
+  "save changes", "git commit", "stage and commit".
+user-invocable: true
+argument-hint: "[optional commit message]"
+allowed-tools: "Read, Grep, Glob, Bash(git *)"
+genskills-version: "1.0.0"
+genskills-category: "workflow"
+genskills-depends: []
+---
+
+# Git Commit
+
+Create structured, well-described git commits.
+
+## Process
+
+### Step 1: Analyze Changes
+- Run `git status` to see all changed files
+- Run `git diff` (unstaged) and `git diff --cached` (staged)
+- If nothing is staged, analyze unstaged changes for smart staging
+
+### Step 2: Smart Staging
+If no files are staged:
+- Group related changes logically
+- Suggest which files should be committed together
+- Stage the appropriate files using `git add <specific files>`
+- Never use `git add -A` — always be explicit
+
+### Step 3: Generate Commit Message
+If `$ARGUMENTS` is provided, use it as the commit message.
+Otherwise, generate one:
+
+**Conventional Commit Format:**
+```
+<type>(<scope>): <description>
+
+<body>
+
+<footer>
+```
+
+**Types**: feat, fix, docs, style, refactor, perf, test, build, ci, chore
+**Scope**: The module/component affected
+**Description**: Imperative mood, no period, max 72 chars
+**Body**: What and why (not how)
+
+### Step 4: Commit
+- Create the commit with the generated message
+- Show the commit hash and summary
+- Never use `--no-verify` — if hooks fail, report the issue
+
+### Step 5: Post-commit
+- Show `git log --oneline -5` for context
+- Suggest next steps (push, create PR, continue working)

package/skills/workflow/pr-create/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: genskills:pr-create
+description: >
+  Create pull requests with AI-generated titles, descriptions, and test plans.
+  Triggers on: "create PR", "open PR", "pull request", "make PR", "submit PR".
+user-invocable: true
+argument-hint: "[base branch, defaults to main]"
+allowed-tools: "Read, Grep, Glob, Bash(git *), Bash(gh *)"
+genskills-version: "1.0.0"
+genskills-category: "workflow"
+genskills-depends:
+  - genskills:git-commit
+---
+
+# PR Create
+
+Create well-documented pull requests.
+
+## Process
+
+### Step 1: Analyze Branch
+- Determine the base branch (from `$ARGUMENTS` or default to main/master)
+- Run `git log <base>..HEAD` to see all commits on this branch
+- Run `git diff <base>...HEAD` to see the full diff
+- Check if the branch is pushed to remote
+
+### Step 2: Generate PR Content
+**Title**: Short (under 70 chars), descriptive, imperative mood
+**Description**:
+```markdown
+## Summary
+<1-3 bullet points describing what this PR does and why>
+
+## Changes
+<Grouped list of significant changes>
+
+## Test Plan
+<How to verify this PR works>
+- [ ] Unit tests pass
+- [ ] Manual testing steps
+
+## Screenshots
+<If UI changes, suggest adding screenshots>
+```
+
+### Step 3: Push and Create
+- Push the branch if not already pushed: `git push -u origin <branch>`
+- Create the PR using: `gh pr create --title "..." --body "..."`
+- Add labels if applicable
+
+### Step 4: Report
+- Show the PR URL
+- List reviewers to consider adding