@caddis/cli 0.0.0 → 0.1.0

package/bundles/antigravity-plugin/skills/gh-cli/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: gh-cli
+description: "GitHub CLI operations — issues, PRs, releases, and repo management"
+---
+
+# GitHub CLI Operations
+
+Practical reference for `gh` — the GitHub CLI. Covers repos, issues, PRs, releases, Actions, and automation.
+
+## Prerequisites
+
+```bash
+# Install
+brew install gh          # macOS
+winget install GitHub.cli # Windows
+sudo apt install gh       # Linux
+
+# Authenticate and verify
+gh auth login
+gh auth status
+```
+
+## Phase 1: Repositories
+
+```bash
+# Create and clone
+gh repo create my-project --public --description "My project" --clone
+gh repo clone owner/repo
+gh repo fork owner/repo --clone
+
+# View and edit
+gh repo view owner/repo
+gh repo edit --description "Updated desc"
+gh browse                  # Open in browser
+
+# Sync fork
+gh repo sync
+```
+
+## Phase 2: Issues
+
+```bash
+# Create
+gh issue create --title "Bug: login broken" --labels bug --assignee @me
+
+# List and search
+gh issue list
+gh issue list --labels bug --assignee @me
+gh issue list --search "is:open label:bug sort:updated-desc"
+gh issue list --json number,title --jq '.[].title'
+
+# Manage
+gh issue view 42
+gh issue close 42 --comment "Fixed in PR #55"
+gh issue edit 42 --add-label priority-high
+gh issue develop 42 --branch fix/issue-42
+```
+
+## Phase 3: Pull Requests
+
+```bash
+# Create
+gh pr create --title "feat: add dark mode" --body "Closes #42" --reviewer user
+gh pr create --draft --title "WIP: new feature"
+
+# List and view
+gh pr list
+gh pr list --author @me
+gh pr view 55
+gh pr diff 55
+
+# Review and merge
+gh pr checkout 55
+gh pr review 55 --approve --body "LGTM!"
+gh pr review 55 --request-changes --body "Please fix error handling"
+gh pr merge 55 --squash --delete-branch
+
+# Manage
+gh pr ready 55             # Mark draft as ready
+gh pr checks 55 --watch    # Watch CI
+gh pr edit 55 --add-label reviewed
+gh pr update-branch 55     # Rebase with base
+```
+
+## Phase 4: Releases
+
+```bash
+# Create
+gh release create v1.2.0 --generate-notes --title "v1.2.0"
+gh release create v1.2.0 --notes-file CHANGELOG.md
+gh release create v1.2.0 ./dist/*.tar.gz   # With assets
+
+# Manage
+gh release list
+gh release view v1.2.0
+gh release download v1.2.0 --pattern "*.tar.gz" --dir ./downloads
+gh release upload v1.2.0 ./dist/checksums.txt
+gh release delete v1.2.0 --yes
+```
+
+## Phase 5: GitHub Actions
+
+```bash
+# Monitor
+gh run list
+gh run list --workflow ci.yml
+gh run view 123456 --log
+gh run watch 123456
+gh run download 123456 --dir ./artifacts
+
+# Trigger
+gh workflow run deploy.yml
+gh workflow run deploy.yml --raw-field environment=staging
+
+# Manage
+gh run rerun 123456
+gh run cancel 123456
+
+# Secrets and variables
+gh secret list
+echo "value" | gh secret set API_KEY
+gh secret set DB_PASS --env production
+gh variable set DEPLOY_ENV --body "staging"
+```
+
+## Phase 6: Advanced
+
+### API Requests
+
+```bash
+gh api /repos/owner/repo/contributors --jq '.[].login'
+gh api --method POST /repos/owner/repo/issues \
+  --field title="API issue" --field body="Created via gh api"
+```
+
+### Bulk Operations
+
+```bash
+# Close stale issues
+gh issue list --search "label:stale" --json number --jq '.[].number' | \
+  xargs -I {} gh issue close {} --comment "Closing as stale"
+
+# Label all open PRs
+gh pr list --json number --jq '.[].number' | \
+  xargs -I {} gh pr edit {} --add-label needs-review
+```
+
+### Search
+
+```bash
+gh search repos "topic:fastapi stars:>100" --json name,url
+gh search code "def authenticate" --repo owner/repo
+gh search issues "label:bug state:open" --limit 20
+```
+
+### Aliases
+
+```bash
+gh alias set co 'pr checkout'
+gh alias set myissues 'issue list --assignee @me'
+gh alias set review 'pr list --search "review-requested:@me"'
+```
+
+## Common Workflows
+
+### Issue to PR (Full Cycle)
+
+```bash
+gh issue develop 42 --branch fix/issue-42
+git add . && git commit -m "fix: resolve login bug" && git push -u origin HEAD
+gh pr create --title "fix: resolve login bug" --body "Closes #42"
+gh pr checks --watch
+gh pr merge --squash --delete-branch
+```
+
+### Release Workflow
+
+```bash
+git tag v1.3.0 && git push origin v1.3.0
+gh release create v1.3.0 --generate-notes --title "v1.3.0"
+gh release upload v1.3.0 ./dist/*.tar.gz
+```
+
+## Quick Reference
+
+| Task              | Command                                        |
+|-------------------|------------------------------------------------|
+| Create repo       | `gh repo create name --public`                 |
+| Create issue      | `gh issue create --title "..." --labels bug`   |
+| Create PR         | `gh pr create --title "..." --reviewer user`   |
+| Merge PR          | `gh pr merge 55 --squash --delete-branch`      |
+| Create release    | `gh release create v1.0.0 --generate-notes`    |
+| Watch CI          | `gh run watch`                                 |
+| Set secret        | `echo "val" \| gh secret set KEY`              |
+| API call          | `gh api /repos/o/r --jq '.description'`        |

package/bundles/antigravity-plugin/skills/git-commit/SKILL.md

@@ -0,0 +1,285 @@
+---
+name: git-commit
+description: Create well-structured conventional commit messages following Conventional Commits standard. Use when committing changes, preparing PRs, or generating changelogs.
+---
+
+# Git Commit Skill
+
+Create meaningful, conventional commit messages that follow team standards.
+
+## Trigger
+
+Activate when:
+- User asks to commit changes
+- User needs help writing a commit message
+- User asks "what should I commit this as?"
+
+---
+
+## Conventional Commit Format
+
+```
+<type>(<scope>): <subject>
+
+[optional body]
+
+[optional footer]
+```
+
+### Types
+
+| Type | Description | Example |
+|------|-------------|---------|
+| `feat` | New feature | `feat(complaints): add priority filtering` |
+| `fix` | Bug fix | `fix(auth): resolve session timeout issue` |
+| `docs` | Documentation | `docs: update API documentation` |
+| `style` | Formatting (no code change) | `style: fix indentation in models` |
+| `refactor` | Code restructuring | `refactor(db): extract query builder` |
+| `perf` | Performance improvement | `perf: add caching to dashboard` |
+| `test` | Adding/fixing tests | `test: add complaint service tests` |
+| `chore` | Maintenance | `chore: update dependencies` |
+| `ci` | CI/CD changes | `ci: add pytest to GitHub Actions` |
+| `build` | Build system/dependencies | `build: update webpack to v5` |
+| `revert` | Revert a previous commit | `revert: revert feat(api) endpoint` |
+
+### Scope
+
+Optional area of change:
+- `api` - Backend API changes
+- `ui` - Frontend/Streamlit changes
+- `db` - Database changes
+- `auth` - Authentication
+- `complaints` - Complaints feature
+- `analytics` - Analytics feature
+
+---
+
+## Phase 1: Analyze Changes
+
+### Actions
+
+0. **Run a pre-commit quality gate (blocking)**
+   ```bash
+   # Python repos
+   ruff check .
+
+   # TypeScript/React repos
+   npm run lint
+
+   # If both stacks exist, run both.
+   ```
+
+   If lint fails, do not proceed to commit generation until fixed.
+
+1. **Review staged changes**
+   ```bash
+   # If files are staged, use staged diff
+   git diff --staged --stat
+   git diff --staged
+
+   # If nothing staged, check working tree
+   git diff
+   git status --porcelain
+   ```
+
+2. **Stage files if needed**
+   ```bash
+   # Stage specific files
+   git add path/to/file1 path/to/file2
+
+   # Stage by pattern
+   git add *.test.*
+   git add src/components/*
+   ```
+
+   **Never stage secrets** (`.env`, `credentials.json`, private keys).
+
+3. **Categorize the changes**
+   - What files were modified?
+   - What was the primary purpose?
+   - Are there multiple logical changes?
+
+3. **Identify the commit type**
+   - New functionality → `feat`
+   - Bug fix → `fix`
+   - Code improvement without behavior change → `refactor`
+   - Tests → `test`
+   - Documentation → `docs`
+
+---
+
+## Phase 2: Craft the Message
+
+### Subject Line Rules
+
+1. **Use imperative mood**: "add" not "added" or "adds"
+2. **No period** at the end
+3. **50 characters or less** (hard limit: 72)
+4. **Lowercase** after the colon
+
+```
+# ✅ Good
+feat(complaints): add priority filter to dashboard
+fix(api): handle null customer_id in query
+refactor(db): extract database adapter class
+
+# ❌ Bad
+feat(complaints): Added priority filter to dashboard.  # Past tense, period
+FEAT: ADD PRIORITY FILTER  # Uppercase, no scope
+fix: various bug fixes  # Too vague
+```
+
+### Body (When Needed)
+
+Include body when:
+- Change needs explanation
+- There's context that isn't obvious
+- Breaking changes exist
+
+```
+feat(api): add complaint analytics endpoint
+
+Add new endpoint for retrieving complaint statistics
+including resolution times, category distribution, and
+trend analysis.
+
+This endpoint powers the new analytics dashboard.
+```
+
+### Footer (When Needed)
+
+```
+# Breaking change
+feat(api)!: change complaint response format
+
+BREAKING CHANGE: complaint.created_at now returns ISO format
+
+# Issue reference
+fix(ui): resolve dashboard loading error
+
+Fixes #123
+```
+
+---
+
+## Phase 3: Generate Message
+
+### Template
+
+Based on the changes, generate:
+
+```markdown
+## Suggested Commit Message
+
+```
+<type>(<scope>): <subject>
+
+<body if needed>
+```
+
+### Reasoning
+- Type: [Why this type was chosen]
+- Scope: [Area of the codebase affected]
+- Subject: [What the change does]
+```
+
+---
+
+## Examples
+
+### Simple Feature
+
+**Changes**: Added a new filter dropdown to the complaints dashboard
+
+```
+feat(ui): add status filter to complaints dashboard
+```
+
+### Bug Fix with Context
+
+**Changes**: Fixed issue where queries with special characters caused errors
+
+```
+fix(db): escape special characters in search queries
+
+The search function was failing when users entered characters
+like quotes or semicolons. Added proper escaping using
+parameterized queries.
+
+Fixes #42
+```
+
+### Refactoring
+
+**Changes**: Moved database logic from routes to repository classes
+
+```
+refactor(api): extract database operations to repository layer
+
+Move direct database calls from route handlers to dedicated
+repository classes. This improves testability and follows
+the separation of concerns principle.
+```
+
+### Multiple Files, Single Purpose
+
+**Changes**: Updated multiple files to add logging
+
+```
+feat: add structured logging throughout application
+
+- Add loguru configuration in config.py
+- Replace print statements with logger calls
+- Add request logging middleware
+```
+
+### Breaking Change
+
+**Changes**: Changed API response format
+
+```
+feat(api)!: standardize API response envelope
+
+BREAKING CHANGE: All API responses now wrapped in
+{ "data": ..., "meta": { "timestamp": ... } } format.
+
+Clients need to update response parsing logic.
+```
+
+---
+
+## Quick Reference
+
+When in doubt, ask yourself:
+
+1. **What type of change is this?** → Choose type
+2. **What area does it affect?** → Choose scope
+3. **What does it do?** (in imperative) → Write subject
+4. **Why was this done?** → Write body if needed
+5. **Does it break anything?** → Add BREAKING CHANGE if yes
+
+---
+
+## Git Safety Protocol
+
+- NEVER update git config
+- NEVER run destructive commands (`--force`, hard reset) without explicit user request
+- NEVER skip hooks (`--no-verify`) unless user asks
+- NEVER force push to main/master
+- ALWAYS verify lint gate status before creating a commit message
+- If a commit fails due to pre-commit hooks, fix the issue and create a NEW commit (don't amend the failed one)
+- One logical change per commit
+- Reference issues in footers: `Closes #123`, `Refs #456`
+
+---
+
+## Commit Message Checklist
+
+- [ ] Type is appropriate for the change
+- [ ] Scope identifies the affected area
+- [ ] Subject uses imperative mood
+- [ ] Subject is under 50 characters
+- [ ] Body explains "why" if not obvious
+- [ ] Breaking changes are marked with `!` and footer
+- [ ] Related issues are referenced
+- [ ] No secrets or credentials in staged files