agentsclimarketplace

Github ci

Skill event4u-app/agent-config/src/skills/github-ci

Use when working with GitHub Actions — workflow YAML, quality gates, test matrices, deployment triggers, reusable workflows — even when the user just says 'my CI is failing' or 'add a check'.From its SKILL.md

Install
npx -y skills add event4u-app/agent-config --skill github-ci

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

github-ci

When to use

Use this skill when working with GitHub Actions workflows, CI pipeline configuration, or understanding the automated quality and deployment process.

Procedure: Modify CI workflows

  1. Read .github/workflows/ to understand the full pipeline.
  2. Check AGENTS.md for quality tool commands and testing setup.
  3. Read commands/fix/ci.md for CI failure debugging workflow.

Workflow overview

Quality pipeline (quality-tests.yml)

Triggered on: pull_request to main, workflow_dispatch

Read .github/workflows/ to discover the actual job matrix. Common patterns:

  • PHP version is extracted from Dockerfile (ARG PHP_VERSION), not hardcoded.
  • Static analysis may run on larger runners for memory.
  • Tests run in parallel with a matrix strategy per test suite.
  • Branch comparison for dead code and API docs.

Deployment workflows

WorkflowTriggerEnvironment
deploy-review.yamlPR with review-env labelReview (ephemeral)
deploy-sta.yamlPush to mainStage
deploy-pro.yamlTag release-X.Y.Z or schedule (Mon 8AM)Production
deploy.ymlAfter "Static Code Analysis" succeeds on mainEnvoyer trigger
module-deploy.yamlReusable workflow (called by others)Parameterized

Other workflows

WorkflowPurpose
pr-review-gate.yamlPoints-based review system (see code-review skill)
destroy-review.yamlCleanup ephemeral review environments
add-labels.ymlAuto-label PRs
apply-pr-template.yamlApply PR description template
validate-deployment-files.yamlValidate AWS deployment configs
template-db-dump.yamlDatabase dump utility

Conventions

Workflow structure

  • Use pinned action versions with SHA hashes (not tags): actions/checkout@<sha> # v6.0.2
  • Use concurrency groups to prevent duplicate runs: group: ${{ github.workflow }}-${{ github.ref }}
  • Use fail-fast: false in matrix strategies for independent job execution.
  • Extract shared logic into reusable workflows (module-deploy.yaml pattern).

Composer auth

Every workflow that installs dependencies needs:

  1. COMPOSER_AUTH secret validation (check if set, validate JSON).
  2. Fallback handling if auth is missing or masked.

PHP version

  • Never hardcode the PHP version in workflows.
  • Always extract from Dockerfile: awk -F= '/^ARG PHP_VERSION/ {print $2}' .docker/Dockerfile
  • Pass via job outputs to dependent jobs.

Runners

Check .github/workflows/ for the runner types used. Common patterns:

  • Standard runners (ubuntu-latest) for light jobs.
  • Larger or custom runners for heavy jobs (static analysis, tests).
  • ARM runners if the project deploys to ARM-based infrastructure.

Environment variables

  • Use env: at job level for shared secrets.
  • Use $GITHUB_OUTPUT for passing data between steps.
  • Use $GITHUB_ENV for variables needed across multiple steps.

Debugging CI failures

  1. Get the failing run: GET /repos/{owner}/{repo}/actions/runs?branch={branch}
  2. Get failed jobs: GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs
  3. Get logs: GET /repos/{owner}/{repo}/actions/jobs/{job_id}/logs
  4. Fix locally, verify in container, then push.

See commands/fix/ci.md for the full debugging workflow.

Output format

  1. Modified workflow YAML file(s) in .github/workflows/
  2. Summary of pipeline changes and affected triggers

Auto-trigger keywords

  • GitHub Actions
  • CI/CD
  • workflow
  • pipeline
  • quality checks

Gotcha

  • CI workflows run on Ubuntu, not macOS — don't assume macOS-specific tools are available.
  • The model forgets to add --env=testing to artisan commands in CI — tests will hit the wrong database.
  • Secret names are case-sensitive in GitHub Actions — double-check the casing.
  • Don't add continue-on-error: true to hide failures — fix the actual error.

Do NOT

  • Do NOT use unpinned action versions (e.g., actions/checkout@v4).
  • Do NOT hardcode PHP versions — always extract from Dockerfile.
  • Do NOT add new secrets without documenting them.
  • Do NOT change runner types without considering cost and architecture (ARM vs x86).

What ships with it: 1 file

1.0 KB alongside SKILL.md

evals/

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.