From ai-toolkit
Provides GitHub Actions patterns for CI/CD pipelines, PR automation, testing workflows, and deployments. Use for setup, fixing broken pipelines, PR checks, or multi-environment deploys.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-toolkit:ci-cd-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Patterns for GitHub Actions, PR automation, and deployment workflows.
Patterns for GitHub Actions, PR automation, and deployment workflows.
name: CI
on:
push:
branches: [main, develop]
pull_request:
branches: [main, develop]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run tests
run: ./gradlew test
name: PR Check
on: pull_request
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: ./gradlew ktlintCheck
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: ./gradlew test
build:
runs-on: ubuntu-latest
needs: [lint, test]
steps:
- uses: actions/checkout@v4
- run: ./gradlew build
Monitor a PR through CI, handle common failures:
gh pr checks <number>gh run rerun <run-id> --failedgh pr merge <number> --auto --squashSee
workflows.mdfor ready-to-use GitHub Actions YAML templates.
Before deploying:
actions/cache or actions/setup-java with cache). A cold Gradle build takes 3-5 minutes, cached takes 30 seconds.needs: creates sequential dependencies. Without it, all jobs run in parallel. Use needs: [lint, test] to make build wait for checks.secrets.DB_PASSWORD and secrets.db_password are different. Match the exact name from Settings > Secrets.actions/checkout@v3 --- use v4. v3 uses Node 16 which is deprecated. v4 uses Node 20.[skip ci]) unless it's docs-onlynpx claudepluginhub c0x12c/ai-toolkit --plugin ai-toolkitProvides GitHub Actions patterns for CI/CD pipelines, release automation with semantic-release, changesets, goreleaser, and testing strategies including matrix, cache, secrets, and reusable workflows.
Provides CI/CD pipeline patterns for GitHub Actions, GitLab CI, Jenkins: caching, matrix builds, OIDC secrets, deployment strategies, optimization. Use for designing, optimizing, troubleshooting pipelines.
Provides CI/CD pipeline patterns for GitHub Actions and GitLab CI, including testing strategies, deployment automation, and reusable actions.