Agent skill

github-workflow

Write and edit GitHub Actions workflow files. Use when creating new workflows, editing existing .github/workflows/*.yml files, or setting up CI/CD pipelines. Triggers on requests like "create a workflow", "add GitHub Actions", "set up CI", or "edit the workflow file".

View SKILL.md on GitHub Repository
Stars 3
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/yaakaito/env/tree/main/dotfiles/.claude/skills/github-workflow

SKILL.md

GitHub Workflow

Write clear, minimal GitHub Actions workflow files.

Naming Guidelines

Do NOT name

  • run steps that are self-explanatory from the command itself
  • uses steps for common, obvious actions like:
    • actions/checkout
    • actions/setup-node
    • oven-sh/setup-bun
    • pnpm/action-setup
    • actions/cache

DO name

  • uses steps with actions/github-script (explain what the script does)
  • Complex multi-line shell scripts (summarize the purpose)
  • Steps where the intent is not obvious from the code

Examples

Good

yaml
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun install
      - run: bun run build
      - run: bun test

      - name: Post build status to Slack
        uses: actions/github-script@v7
        with:
          script: |
            const webhook = process.env.SLACK_WEBHOOK;
            // ... complex logic

Bad

yaml
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
      - name: Setup Bun
        uses: oven-sh/setup-bun@v2
      - name: Install dependencies
        run: bun install
      - name: Build project
        run: bun run build
      - name: Run tests
        run: bun test

Best Practices

  • Pin action versions with full SHA or major version tag (@v4, not @main)
  • Use workflow_dispatch for manual triggers when useful
  • Set appropriate permissions to follow least privilege
  • Use concurrency to cancel redundant runs
  • Prefer ${{ github.token }} over PAT when possible
  • Avoid emoji in workflow names and step names
  • Use $GITHUB_STEP_SUMMARY to output execution results in Markdown format
  • Avoid obvious comments; only add comments to explain complex logic

Step Summary Example

yaml
- name: Report test results
  run: |
    echo "## Test Results" >> $GITHUB_STEP_SUMMARY
    echo "| Suite | Passed | Failed |" >> $GITHUB_STEP_SUMMARY
    echo "|-------|--------|--------|" >> $GITHUB_STEP_SUMMARY
    echo "| Unit  | 42     | 0      |" >> $GITHUB_STEP_SUMMARY

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

yaakaito/env

spec-file-manager

Manage specification files. Use when creating, reading, updating, or listing spec files. Triggers on requests like "create spec", "update spec", "list specs", or "show spec status".

3 0
Explore
yaakaito/env

adr-writer

Skill for creating and editing Architecture Decision Records (ADRs). Use when requests involve "create ADR", "record architecture decision", or "document design decisions". Supports creating new ADRs, updating existing ADRs, and reviewing ADR format.

3 0
Explore
yaakaito/env

github-pr-unresolved-review-fetcher

Fetch unresolved PR review comments from GitHub. Use when working with pull request reviews, addressing review feedback, or checking outstanding review comments on a PR. Triggers on requests like "get PR reviews", "fetch review comments", "show unresolved comments", or "what feedback is pending on this PR".

3 0
Explore
yaakaito/env

github-workflow-fixer

Analyze and fix GitHub Actions workflow failures. Use when workflows fail, CI/CD issues occur, or when debugging GitHub Actions runs. Triggers on requests like "fix workflow", "why did the build fail", "check CI status", "debug GitHub Actions", or "workflow failed".

3 0
Explore
yaakaito/env

codex-review

Codex CLI を使って現在のコード変更を5つの観点（セキュリティ・パフォーマンス・バグ・テスト・アーキテクチャ）から並列レビューし、指摘に基づいてコードを修正するスキル。ユーザーが「codex でレビュー」「codex review」「コードレビューして」「レビュー実行」「codex にレビューさせて」「変更をチェック」などと言った場合や、コード品質チェック・多角的なレビューを求められた場合に使用する。明示的に codex に言及していなくても、包括的なコードレビューを求められたらこのスキルの使用を検討すること。

3 0
Explore
yaakaito/env

research

Research a topic using WebSearch based on the current context. Use when the user needs best practices, external guidance, or wants to investigate approaches. Triggers on "research", "search best practices", "find examples".

3 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results