From hatch3r
Sets up AI-powered CI/CD agentic workflows for repository automation using GitHub Actions (default), Azure Pipelines, and GitLab CI. Provides templates for continuous test improvement, issue triage, and documentation updates.
npx claudepluginhub hatch3r/hatch3rThis skill uses the workspace's default tool permissions.
> **Platform detection:** Check `platform` in `.agents/hatch.json` to determine which CI/CD system to use. Defaults to `"github"`.
Designs CI/CD pipelines and GitHub Actions workflows to automate builds, tests, deployments, and development processes with quality gates and security.
Designs and implements CI/CD pipelines, GitHub Actions workflows, and automation for build/test/deploy processes to reduce manual work and ensure quality/security.
Designs GitHub Actions workflows for CI/CD pipelines, covering triggers, jobs, matrix builds, caching, reusable workflows, security, and best practices. Use for creating or reviewing automation.
Share bugs, ideas, or general feedback.
Platform detection: Check
platformin.agents/hatch.jsonto determine which CI/CD system to use. Defaults to"github".
This skill guides setup for AI-powered CI/CD automation in hatch3r-managed projects. The core SKILL covers GitHub Actions (the default); non-GitHub platforms load on demand from references/.
| Target platform | File to read |
|---|---|
| GitHub Actions (default) | This file — read sections below |
| Azure DevOps Pipelines | references/azure-devops.md |
| GitLab CI/CD | references/gitlab-ci.md |
Load only the references file that matches platform in .agents/hatch.json. Do not eagerly load all three.
GitHub Agentic Workflows (technical preview, Feb 2026) bring AI agent orchestration into GitHub Actions. Agentic Workflows are markdown files in .github/workflows/ with YAML frontmatter that compile to GitHub Actions jobs. They support multiple AI engines (GitHub Copilot, Claude, OpenAI Codex) and use MCP for tool access.
Automatically assess test coverage and add high-value tests.
# .github/workflows/hatch3r-continuous-testing.md
---
name: Continuous Test Improvement
on:
schedule:
- cron: '0 6 * * 1'
workflow_dispatch:
engine: copilot
permissions:
contents: read
pull-requests: write
---
Analyze test coverage gaps and open PRs with new tests for uncovered critical paths.
Automatically summarize, label, and route new issues.
# .github/workflows/hatch3r-continuous-triage.md
---
name: Continuous Triage
on:
issues:
types: [opened]
engine: copilot
permissions:
issues: write
---
When a new issue is opened, analyze it, apply labels from the hatch3r taxonomy (type:, priority:, area:*), and add a triage summary comment.
Keep documentation aligned with code changes.
# .github/workflows/hatch3r-continuous-docs.md
---
name: Continuous Documentation
on:
pull_request:
types: [closed]
branches: [{defaultBranch}]
engine: copilot
permissions:
contents: write
pull-requests: write
---
Replace {defaultBranch} with board.defaultBranch from .agents/hatch.json (fallback: "main").
After a PR is merged, check if documentation needs updating and open a follow-up PR.
.github/workflows/ using the templates aboveFor Azure DevOps setup: see references/azure-devops.md. For GitLab setup: see references/gitlab-ci.md.
gh workflow view {name} or the Actions web UIgh workflow run {name} → gh run watchPlatform-equivalent verification for ADO/GitLab: see the platform reference files.
gh run list --workflow={name}actionlint for GitHub Actions). Fix all reported errors before committing.timeout-minutes to the workflow, scope file references to reduce context size, and add concurrency groups to prevent parallel runs.| Symptom | Likely Cause | Fix |
|---|---|---|
| Workflow doesn't trigger | Incorrect on: event or branch filter | Verify event type matches, check branch protection rules |
| AI output is empty/poor | Insufficient context in workflow body | Add more context, reference specific files, include examples |
| Permission denied | Missing or insufficient permissions | Add required permissions in frontmatter, check org policies |
| MCP tool fails | Server not available or misconfigured | Verify MCP server is accessible, check auth tokens |
| Rate limiting | Too many workflow runs | Add concurrency groups, reduce trigger frequency |
| Workflow hangs | Large repo context or slow AI response | Set timeout-minutes, scope file references |
If a workflow produces undesirable results:
gh workflow disable {name} or toggle in repo Settings → Actionsgh run view {run-id} --logPlatform-equivalent rollback for ADO/GitLab: see the platform reference files.
.github/workflows/, azure-pipelines/, .gitlab-ci.yml)workflow_dispatch / manual pipeline run / manual pipeline trigger)