@waoooo/claude-skills 1.0.0

package/skills/github-actions-trigger/SKILL.md

@@ -0,0 +1,367 @@
+---
+name: github-actions-trigger
+description: Trigger and monitor GitHub Actions workflows. Use when you need to run tests, build, deploy, or check workflow status. Can wait for completion and report results.
+---
+
+# GitHub Actions Trigger
+
+Trigger GitHub Actions workflows and monitor their execution.
+
+## Current repository
+
+!`gh repo view --json nameWithOwner -q '.nameWithOwner' 2>/dev/null || echo "Not in a git repository"`
+
+## Core workflow
+
+### 1. List available workflows
+
+```bash
+gh workflow list
+```
+
+### 2. Trigger workflow
+
+```bash
+gh workflow run <workflow-name-or-id> --ref <branch>
+```
+
+### 3. Monitor workflow run
+
+```bash
+# Watch the latest run
+gh run watch
+
+# View specific run
+gh run view <run-id>
+```
+
+## Common use cases
+
+### Use Case 1: Run tests (Product Builder Step 16)
+
+When task verification needs to run tests:
+
+```bash
+# Trigger test workflow
+gh workflow run test.yml --ref feature/pricing-system
+
+# Wait for completion
+gh run watch
+
+# Get result
+gh run view --log
+```
+
+### Use Case 2: Run specific workflow with inputs
+
+```bash
+gh workflow run deploy.yml \
+  --ref main \
+  --field environment=staging \
+  --field version=1.2.0
+```
+
+### Use Case 3: Check workflow status
+
+```bash
+# List recent runs
+gh run list --limit 5
+
+# View specific run
+gh run view 123456
+
+# Get logs
+gh run view 123456 --log
+```
+
+### Use Case 4: Re-run failed workflow
+
+```bash
+# Re-run failed jobs
+gh run rerun 123456 --failed
+
+# Re-run all jobs
+gh run rerun 123456
+```
+
+## Workflow commands
+
+### List workflows
+
+```bash
+# List all workflows
+gh workflow list
+
+# List with more details
+gh workflow list --all
+```
+
+### View workflow
+
+```bash
+# View workflow details
+gh workflow view <workflow-name-or-id>
+
+# View workflow runs
+gh run list --workflow=<workflow-name>
+```
+
+### Trigger workflow
+
+```bash
+# Basic trigger
+gh workflow run <workflow-name>
+
+# With branch
+gh workflow run <workflow-name> --ref feature/branch
+
+# With inputs
+gh workflow run <workflow-name> \
+  --field key1=value1 \
+  --field key2=value2
+```
+
+## Run commands
+
+### List runs
+
+```bash
+# List recent runs
+gh run list
+
+# List runs for specific workflow
+gh run list --workflow=test.yml
+
+# List runs with status
+gh run list --status=failure
+```
+
+### View run
+
+```bash
+# View run summary
+gh run view <run-id>
+
+# View run logs
+gh run view <run-id> --log
+
+# View specific job logs
+gh run view <run-id> --job=<job-id> --log
+```
+
+### Watch run
+
+```bash
+# Watch latest run
+gh run watch
+
+# Watch specific run
+gh run watch <run-id>
+```
+
+### Cancel run
+
+```bash
+gh run cancel <run-id>
+```
+
+### Re-run
+
+```bash
+# Re-run failed jobs
+gh run rerun <run-id> --failed
+
+# Re-run all jobs
+gh run rerun <run-id>
+```
+
+## Integration with Product Builder
+
+### Step 16: Task Verification
+
+After completing a task, trigger tests:
+
+```bash
+# 1. Trigger test workflow
+WORKFLOW_RUN=$(gh workflow run test.yml --ref $(git branch --show-current) --json)
+
+# 2. Wait for completion
+gh run watch
+
+# 3. Check result
+RESULT=$(gh run view --json conclusion -q '.conclusion')
+
+if [ "$RESULT" = "success" ]; then
+  echo "✅ Tests passed"
+else
+  echo "❌ Tests failed"
+  # Create issue for failure
+  gh issue create \
+    --title "Test failure in task verification" \
+    --body "Tests failed. See run: $(gh run view --json url -q '.url')" \
+    --label "test-failure,bug"
+fi
+```
+
+## Workflow file examples
+
+### Basic test workflow (.github/workflows/test.yml)
+
+```yaml
+name: Test
+
+on:
+  workflow_dispatch:  # Allow manual trigger
+  push:
+    branches: [feature/*]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: '18'
+      - run: npm ci
+      - run: npm test
+```
+
+### Workflow with inputs (.github/workflows/deploy.yml)
+
+```yaml
+name: Deploy
+
+on:
+  workflow_dispatch:
+    inputs:
+      environment:
+        description: 'Environment to deploy to'
+        required: true
+        type: choice
+        options:
+          - staging
+          - production
+      version:
+        description: 'Version to deploy'
+        required: true
+        type: string
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - run: echo "Deploying ${{ inputs.version }} to ${{ inputs.environment }}"
+```
+
+## Important rules
+
+- **ALWAYS** specify branch with `--ref` when triggering
+- **ALWAYS** wait for completion before checking results
+- **ALWAYS** check workflow status before assuming success
+- **NEVER** trigger workflows on main without confirmation
+- Use `gh run watch` to monitor progress
+- Create Issue if workflow fails
+
+## Error handling
+
+### Workflow not found
+
+```bash
+# List available workflows
+gh workflow list
+
+# Use exact workflow name or ID
+gh workflow run test.yml
+```
+
+### Workflow run failed
+
+```bash
+# View logs to see error
+gh run view <run-id> --log
+
+# Create issue for tracking
+gh issue create \
+  --title "Workflow failed: <workflow-name>" \
+  --body "Run: <run-url>" \
+  --label "ci-failure"
+```
+
+### Permission denied
+
+```bash
+# Check authentication
+gh auth status
+
+# Re-authenticate if needed
+gh auth login
+```
+
+## Examples
+
+### Example 1: Run tests and create issue if failed
+
+```bash
+#!/bin/bash
+
+# Trigger test workflow
+echo "Triggering tests..."
+gh workflow run test.yml --ref $(git branch --show-current)
+
+# Wait a bit for run to start
+sleep 5
+
+# Watch the run
+gh run watch
+
+# Get the latest run result
+RESULT=$(gh run list --limit 1 --json conclusion -q '.[0].conclusion')
+RUN_URL=$(gh run list --limit 1 --json url -q '.[0].url')
+
+if [ "$RESULT" != "success" ]; then
+  echo "❌ Tests failed, creating issue..."
+  gh issue create \
+    --title "Test failure: $(date +%Y-%m-%d)" \
+    --body "$(cat <<EOF
+## Test Failure
+
+Tests failed in workflow run.
+
+## Details
+- Branch: $(git branch --show-current)
+- Commit: $(git rev-parse --short HEAD)
+- Run: $RUN_URL
+
+## Action Required
+Review logs and fix failing tests.
+EOF
+)" \
+    --label "test-failure,bug,priority:high" \
+    --assignee "@me"
+else
+  echo "✅ Tests passed"
+fi
+```
+
+### Example 2: Deploy to staging
+
+```bash
+gh workflow run deploy.yml \
+  --ref main \
+  --field environment=staging \
+  --field version=1.2.0
+
+echo "Deployment triggered. Watching progress..."
+gh run watch
+```
+
+## Notes
+
+- Works in **current directory** (uses current repo)
+- Uses `gh` CLI (GitHub CLI)
+- Requires authentication (`gh auth login`)
+- Requires workflow files in `.github/workflows/`
+- Compatible with any GitHub repository

package/skills/github-issue-create/SKILL.md

@@ -0,0 +1,294 @@
+---
+name: github-issue-create
+description: Create GitHub Issue for tracking problems. Use when multi-model review finds issues, tests fail, or problems need tracking. Automatically adds labels, assignees, and links to related context.
+---
+
+# GitHub Issue Create
+
+Create GitHub Issues to track problems, bugs, and tasks.
+
+## Current repository
+
+!`gh repo view --json nameWithOwner -q '.nameWithOwner' 2>/dev/null || echo "Not in a git repository"`
+
+## Core workflow
+
+### 1. Prepare issue details
+
+**Required information**:
+- Title (clear and concise)
+- Body (detailed description)
+
+**Optional information**:
+- Labels (comma-separated)
+- Assignees (comma-separated usernames)
+- Milestone
+- Project
+
+### 2. Create issue
+
+```bash
+gh issue create \
+  --title "Issue title" \
+  --body "Issue description" \
+  --label "bug,priority:high" \
+  --assignee "@me"
+```
+
+### 3. Get issue URL
+
+The command returns the issue URL, which can be used for tracking.
+
+## Common use cases
+
+### Use Case 1: Multi-model review feedback
+
+When multi-model review (OpenSpec/Specs/Acceptance) finds problems:
+
+```bash
+gh issue create \
+  --title "Review feedback: [Brief description]" \
+  --body "$(cat <<'EOF'
+## Review Type
+OpenSpec Review / Specs Review / Acceptance Review
+
+## Issues Found
+- Issue 1
+- Issue 2
+
+## Context
+- Job: [job-name]
+- Step: [step-number]
+- Review file: [path-to-review-file]
+
+## Action Required
+[What needs to be fixed]
+EOF
+)" \
+  --label "review-feedback,openspec" \
+  --assignee "@me"
+```
+
+### Use Case 2: Test failure
+
+When Actions or tests fail:
+
+```bash
+gh issue create \
+  --title "Test failure: [Test name]" \
+  --body "$(cat <<'EOF'
+## Failed Test
+[Test name or suite]
+
+## Error Message
+```
+[Error output]
+```
+
+## Context
+- Commit: [commit-hash]
+- Branch: [branch-name]
+- Actions run: [actions-url]
+
+## Steps to Reproduce
+1. Step 1
+2. Step 2
+
+## Expected vs Actual
+- Expected: [what should happen]
+- Actual: [what happened]
+EOF
+)" \
+  --label "test-failure,bug" \
+  --assignee "@me"
+```
+
+### Use Case 3: Bug report
+
+```bash
+gh issue create \
+  --title "Bug: [Brief description]" \
+  --body "$(cat <<'EOF'
+## Description
+[Detailed description]
+
+## Steps to Reproduce
+1. Step 1
+2. Step 2
+
+## Expected Behavior
+[What should happen]
+
+## Actual Behavior
+[What actually happens]
+
+## Environment
+- OS: [operating system]
+- Version: [version]
+EOF
+)" \
+  --label "bug" \
+  --assignee "@me"
+```
+
+### Use Case 4: Feature request
+
+```bash
+gh issue create \
+  --title "Feature: [Brief description]" \
+  --body "$(cat <<'EOF'
+## Feature Description
+[What feature do you want]
+
+## Use Case
+[Why is this needed]
+
+## Proposed Solution
+[How should it work]
+
+## Alternatives Considered
+[Other options]
+EOF
+)" \
+  --label "feature,enhancement"
+```
+
+## Important rules
+
+- **ALWAYS** use clear, descriptive titles
+- **ALWAYS** include context (commit, branch, file paths)
+- **ALWAYS** use HEREDOC for multi-line body
+- **ALWAYS** add appropriate labels
+- **NEVER** create duplicate issues (check first with `gh issue list`)
+- Use `@me` to assign to yourself
+
+## Check for duplicates
+
+Before creating, check if similar issue exists:
+
+```bash
+# Search by keyword
+gh issue list --search "keyword"
+
+# List open issues with label
+gh issue list --label "bug" --state open
+```
+
+## Available labels
+
+Check available labels in the repository:
+
+```bash
+gh label list
+```
+
+Common labels:
+- `bug` - Bug reports
+- `feature` - Feature requests
+- `enhancement` - Improvements
+- `docs` - Documentation
+- `test-failure` - Test failures
+- `review-feedback` - Review feedback
+- `priority:critical` - Critical priority
+- `priority:high` - High priority
+- `priority:medium` - Medium priority
+- `priority:low` - Low priority
+
+## Link to related items
+
+### Link to PR
+
+```bash
+gh issue create \
+  --title "Issue title" \
+  --body "Related to #123" \
+  --label "bug"
+```
+
+### Link to commit
+
+```bash
+gh issue create \
+  --title "Issue title" \
+  --body "Introduced in commit abc123" \
+  --label "bug"
+```
+
+## Close issue
+
+When problem is fixed:
+
+```bash
+gh issue close <issue-number> --comment "Fixed in #PR-number"
+```
+
+## Examples
+
+### Example 1: OpenSpec review found issues
+
+```bash
+gh issue create \
+  --title "OpenSpec review: Missing validation for user input" \
+  --body "$(cat <<'EOF'
+## Review Type
+OpenSpec Review (Step 5)
+
+## Issues Found
+- Missing input validation for email field
+- No error handling for API timeout
+
+## Context
+- Job: pricing-system
+- OpenSpec: openspec/changes/001-pricing-system/
+- Review: exports/jobs/2026-02-11-pricing-system/reviews/openspec/gemini/review.md
+
+## Action Required
+1. Add email validation in proposal.md
+2. Add timeout handling in design.md
+EOF
+)" \
+  --label "review-feedback,openspec,priority:high" \
+  --assignee "@me"
+```
+
+### Example 2: Actions test failed
+
+```bash
+gh issue create \
+  --title "Test failure: unit tests for payment gateway" \
+  --body "$(cat <<'EOF'
+## Failed Test
+npm test -- payment-gateway.test.ts
+
+## Error Message
+```
+FAIL src/payment-gateway.test.ts
+  ✕ should handle timeout (1234 ms)
+    Expected: 200
+    Received: 500
+```
+
+## Context
+- Commit: abc123def
+- Branch: feature/pricing-system
+- Actions: https://github.com/owner/repo/actions/runs/123456
+
+## Steps to Reproduce
+1. Run npm test
+2. Test fails on timeout handling
+
+## Expected vs Actual
+- Expected: Return 200 with retry
+- Actual: Return 500 without retry
+EOF
+)" \
+  --label "test-failure,bug,priority:high" \
+  --assignee "@me"
+```
+
+## Notes
+
+- Works in **current directory** (uses current repo)
+- Uses `gh` CLI (GitHub CLI)
+- Requires authentication (`gh auth login`)
+- Compatible with any GitHub repository