Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

github-workflow-automation · sickn33 — Claude Code skill: install & uses

A skill that hands the agent patterns for GitHub work: AI-assisted PR review, issue triage, Actions workflows, CI/CD hooks, rebases and cherry-picks.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill github-workflow-automation -a claude-code
Open on GitHub

What github-workflow-automation does

Reach for it when the job is GitHub-shaped: reviewing pull requests with a model in the loop, sorting incoming issues, writing Actions files, wiring an AI step into CI. The skill file outlines each case, then points to references/detailed-guide.md for the full procedure; that document's safety and validation rules are meant to be treated as mandatory. Load one section for a narrow task, the whole guide for end-to-end work.

It is a sketch, not a switch you flip. analyzeIssue, callAI, ai, execFile and the provider SDK setup are absent, example model and action versions are historical, and multiline output handling is unfinished. Deploy, rebase and rollback ship disabled until real safeguards exist. The author tags the skill risk: critical and asks for authorization before you turn on comments, labels, stale closure, schedules, branch pushes or protection edits.

So treat it as a checklist for a workflow you were going to write anyway. Issue and diff text must not be interpolated into shell or JavaScript: pass it through env vars and files, with argument arrays and validated full SHAs. Fork PRs usually have no secrets or write token, and an honest failure beats a pull_request_target checkout that trusts the fork.

What it helps with

  • review a pull request with a model and keep merge rights human
  • sort new issues into labels without a script per repo
  • draft a GitHub Actions workflow with sane token permissions
  • add an AI step to CI without leaking secrets to forks
  • check permissions and head before a rebase or cherry-pick

Example prompts for the agent

  • Read `references/detailed-guide.md` and draft a PR review workflow where the model cannot approve the merge
  • Audit `.github/workflows/triage.yml` for issue text reaching a shell and rewrite it with env vars
  • Walk the rebase checklist for `feature/x` — which permission and head checks run before any push

How to install github-workflow-automation

1Skills CLI (Vercel)

npx skills add sickn33/agentic-awesome-skills --skill github-workflow-automation -a claude-code

2Manually: put the files in place

~/.claude/skills/github-workflow-automation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/github-workflow-automation/

From the same set80

The whole set →
docker-expert sickn33 A skill that turns your AI agent into a Docker reviewer for Dockerfiles, multi-stage builds and container security. Useful when images and Compose files need a second look. Claude Code CX Codex Cursor +1 27,200installs typescript-expert sickn33 A skill for TypeScript and JavaScript work: it reads your project setup, fixes type errors and speeds up type checking. Useful once a TS codebase gets big. Claude Code CX Codex Cursor +1 12,600installs browser-automation sickn33 This skill builds browser checks around observed UI state and explicit outcomes. Use it for UI workflows, timing failures, or authorised page-data collection. Claude Code CX Codex Cursor +1 6,700installs nextjs-supabase-auth sickn33 This skill wires Supabase Auth into the Next.js App Router with clients, middleware, OAuth callbacks, and Server Actions. Use it when you need protected routes and session handling. Claude Code CX Codex Cursor +1 6,500installs 3d-web-experience sickn33 Helps build and debug web 3D scenes, product configurators, and portfolios. Covers stack choice, model loading, scroll interaction, and performance checks. Claude Code CX Codex Cursor +1 5,200installs prisma-expert sickn33 This skill helps inspect Prisma schemas, migrations, and queries. Use it to investigate an error or review database changes before deployment. Claude Code CX Codex Cursor +1 4,200installs playwright-skill sickn33 Write and run Playwright browser tests directly in Claude Code: responsive design checks, login flows, form submissions, screenshots. Executes locally via Node with a visible browser window. Claude Code CX Codex Cursor +1 3,900installs game-development sickn33 Guides game architecture decisions, platform choices, and core loop structure. Directs the assistant to specialized sub-skills for web, mobile, PC, or VR. Claude Code CX Codex Cursor +1 3,800installs

Other versions of github-workflow-automation

Similar

github-multi-repo ruvnet A skill for coordinating several repositories at once: it aligns package versions, checks cross-package integration and suggests structure changes. Claude Code CX Codex Cursor +1 1,200installs roundup official github Pulls from GitHub, email, Teams and Slack, then drafts a status briefing in your own writing style. Useful when you owe the same update every week. GitHub Copilot 1,300installs conventional-commit-message dangreen Generates changelog-ready commit messages following Conventional Commits 1.0.0 and conventional-changelog presets. It guides AI agents on type selection and breaking changes. Claude Code CX Codex Cursor +1 944installs gh-issue-sync mitsuhiko Syncs GitHub Issues into local Markdown files for triage, search, editing, and issue creation from an editor or terminal. Claude Code CX Codex Cursor +1 23,300installs Hooks Automation ruvnet A hooks system that automatically coordinates Claude Code operations, formats code, and learns from development patterns. Manages agents, persists session context, and integrates with MCP tools. Claude Code CX Codex Cursor +1 1,100installs fix-merge-conflicts cursor Resolves merge conflicts in a branch, then checks the build and tests before wrapping up. Use it when several conflicted files need focused fixes without a refactor. Claude Code CX Codex Cursor +1 2,700installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. Claude Code 990,453installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. Claude Code 789,521installs

Questions about github-workflow-automation

How do I install github-workflow-automation in Claude Code?

Run npx skills add sickn33/agentic-awesome-skills --skill github-workflow-automation -a claude-code. The skill lands at ~/.claude/skills/github-workflow-automation/SKILL.md.

What does github-workflow-automation do?

It describes how the agent should handle GitHub work: PR review, issue triage, Actions workflows, an AI step in CI/CD, rebases and cherry-picks. The full procedure lives in references/detailed-guide.md.

Can I enable it as it stands?

No. Some code and the provider SDK setup are not supplied, deploy, rebase and rollback are disabled until safeguards exist, and the skill is marked risk: critical. The author asks for authorization before enabling labels, schedules or branch pushes.

Source text

SKILL.md · MIT
---
name: github-workflow-automation
description: "Patterns for automating GitHub workflows with AI assistance, inspired by [Gemini CLI](https://github.com/google-gemini/gemini-cli) and modern DevOps practices."
risk: critical
source: community
date_added: "2026-02-27"
---

# 🔧 GitHub Workflow Automation

> Patterns for automating GitHub workflows with AI assistance, inspired by [Gemini CLI](https://github.com/google-gemini/gemini-cli) and modern DevOps practices.

## Detailed Guide

Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

## When to Use This Skill

Use this skill when:

- Automating PR reviews with AI
- Setting up issue triage automation
- Creating GitHub Actions workflows
- Integrating AI into CI/CD pipelines
- Automating Git operations (rebases, cherry-picks)

---

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

## Trust boundaries and missing implementations

These are partial design sketches, not ready-to-enable workflows: analyzeIssue/callAI/ai/execFile and the provider SDK setup are not supplied, example model/action versions are historical, multiline-output handling is incomplete, and deploy/rebase/rollback are deliberately disabled until concrete safeguards exist. Obtain authorization before enabling comments, labels, stale closure, schedules, branch pushes or protection changes. Never interpolate issue/comment/diff/file/branch text into shell or JavaScript source; pass data via environment or private files and use argument arrays with validated full SHAs. Use NUL-delimited Git filenames, random output delimiters or bounded artifact files instead of fixed EOF/multiline one-line outputs. Treat model inputs/results as untrusted; validate structured labels and bounded markdown and never let prompt text authorize tools or approve a PR. Do not execute fork/PR code, package scripts or checked-out actions in a secret/write-token context; use a trusted isolated reviewer, minimal permissions, pinned reviewed action SHAs and restricted network/data transfer. Public/fork PRs normally lack provider secrets/write tokens: fail/skip honestly rather than switching to an unsafe pull_request_target checkout. Check actual maintainer permission via GitHub API, exact command syntax, same-repo branch ownership and current head before any rebase; use an explicit expected-head lease and report conflicts without forceful resolution. Highest version tag is not last successful deployment, AI risk scores do not satisfy deterministic gates, and commit summaries do not describe all deploy changes. Preserve existing protection/ruleset requirements instead of replacing them with an example context list. Unknown changed paths/config/lockfile changes must trigger the full relevant test set; path selection alone is not dependency analysis.

© sickn33 · MIT · sickn33/agentic-awesome-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor