# Github Actions

> Inspect GitHub Actions failures, logs, or permissions and implement requested CI fixes.

- Skill: `alemar11/github-actions` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add alemar11/github-actions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alemar11/github-actions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: alemar11 (https://skillmd.com/u/alemar11)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alemar11/github-actions

---


# GitHub Actions

Use authenticated `gh` directly. Before provider-facing commands, read
[Network execution](../../references/network-execution.md) and complete the
[gh preflight](../../references/gh-dependency-preflight.md).

Keep status, diagnosis, and review requests read-only. An explicit CI fix
request authorizes the smallest implementation and relevant local validation;
remote reruns and publication require their own established authority.

For checks, jobs, and logs, read [workflows.md](references/workflows.md).
Interpret provider lifecycle and conclusions using
[states.md](references/states.md). For workflows that create or approve PRs,
branches, or tags, read [configuration.md](references/configuration.md) before
authoring them. Its repository-settings check is advisory: unavailable settings
do not prevent an explicitly requested workflow edit.

Report the exact repository and PR or commit, failing command and supporting
evidence, actionable diagnosis, pending or unavailable evidence, and relevant
check/run links. An authoritative empty check inventory means no checks were
reported for that target; it proves neither successful CI nor absent workflow
configuration. After a fix, distinguish local validation from remote evidence;
recheck when a new run exists before claiming remote success.