Agent skill
add-workflow
Create a GitHub Actions workflow following x4-mono CI patterns
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/add-workflow
SKILL.md
Add Workflow Skill
Create a new GitHub Actions workflow for x4-mono.
Arguments
The user describes the workflow. If unclear, ask for:
- Workflow name and purpose
- Trigger events (push, PR, schedule, manual)
- Which workspaces/paths should trigger it
- Required secrets or environment variables
File Location
.github/workflows/{name}.yml
Workflow Template
Reference: .github/workflows/ci.yml
name: Workflow Name
on:
push:
branches: [main]
pull_request:
branches: [main]
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
job-name:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: oven-sh/setup-bun@v2
with:
bun-version: '1.3.8'
- uses: actions/cache@v5
with:
path: ~/.bun/install/cache
key: bun-${{ runner.os }}-${{ hashFiles('bun.lock') }}
restore-keys: |
bun-${{ runner.os }}-
- run: bun install --frozen-lockfile
- run: # your command here
Common Patterns
Path Filtering (only run when relevant files change)
jobs:
changes:
runs-on: ubuntu-latest
outputs:
api: ${{ steps.filter.outputs.api }}
web: ${{ steps.filter.outputs.web }}
steps:
- uses: actions/checkout@v4
- uses: dorny/paths-filter@v3
id: filter
with:
filters: |
api:
- 'apps/api/**'
- 'packages/**'
web:
- 'apps/web/**'
- 'packages/**'
api-tests:
needs: changes
if: needs.changes.outputs.api == 'true'
# ...
CI Gate (require all jobs pass)
ci-passed:
needs: [quality, api-tests, web-tests]
if: always()
runs-on: ubuntu-latest
steps:
- run: |
if [[ "${{ contains(needs.*.result, 'failure') }}" == "true" ]]; then
exit 1
fi
Neon Branch (PR database isolation)
neon-branch:
if: github.event_name == 'pull_request'
runs-on: ubuntu-latest
outputs:
db_url: ${{ steps.create-branch.outputs.db_url }}
steps:
- uses: neondatabase/create-branch-action@v6
id: create-branch
with:
project_id: ${{ secrets.NEON_PROJECT_ID }}
api_key: ${{ secrets.NEON_API_KEY }}
branch_name: pr-${{ github.event.number }}
Manual Trigger with Inputs
on:
workflow_dispatch:
inputs:
environment:
description: 'Target environment'
required: true
type: choice
options:
- staging
- production
Scheduled
on:
schedule:
- cron: '0 6 * * 1' # Every Monday at 6 AM UTC
Conventions
- Always use
actions/checkout@v4 - Always use
oven-sh/setup-bun@v2with pinned version - Always cache Bun install cache
- Always use
--frozen-lockfilefor installs - Use concurrency with
cancel-in-progress: true - Gate jobs on path filters to avoid unnecessary runs
- Include a
ci-passedgate if there are multiple parallel jobs
Workflow
- Read
.github/workflows/ci.ymlto understand existing patterns - Create new workflow file at
.github/workflows/{name}.yml - Configure triggers, path filters, and concurrency
- Add Bun setup + cache steps
- Add job-specific steps
- Add CI gate job if there are multiple parallel jobs
- Test by pushing to a branch or using
actlocally
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?