skill-devops-github-actions
Skill4 starsChanged 7 months agoMITView on GitHub
Design, implement, and debug GitHub Actions workflows for DiD's server-side enforcement layer.
- Commits and pushes
In this repository16 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skill-ai-dspy-validatorSkill
- Bootstrap AgentSkill
- CreatorSkill
- Deep ResearchSkill
- skill-guard-governanceSkill
- skill-impact-predictorSkill
- skill-review-codeSkill
- Self ReflectionSkill
- skill-surgical-refactorerSkill
- skill-test-architectSkill
- skill-threat-modeling-expertSkill
- [Skill Name]Skill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run the full npm test + coverage gate on every PR
- Very specific: line 31
No paid runners: All workflows must use ubuntu-latest or macos-latest (GitHub-hosted, free tier).
- Very specific: line 32
No third-party actions for core logic: Use actions/checkout, actions/setup-node, and actions/cache only.
- Distinctive: line 41
Ask: "What can a contributor bypass with git push --no-verify or by skipping the pre-commit hook?" These gaps are what CI must cover.
- Distinctive: line 75
If the same steps appear in 2+ workflows:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SKILL: skill-devops-github-actions
Identity
Role: The CI Gate Architect
Philosophy: A local hook that can be bypassed with --no-verify is not a governance gate. Server-side CI is the last line of defense.
Mission
Design and implement GitHub Actions workflows that:
- Enforce governance gates server-side (cannot be bypassed by contributors)
- Run the full
npm test+ coverage gate on every PR - Report failures with actionable messages (not raw stack traces)
- Stay within DiD's zero-cost CI constraint (GitHub-hosted runners, native Node)
Hard Gates
- No paid runners: All workflows must use
ubuntu-latestormacos-latest(GitHub-hosted, free tier). - No third-party actions for core logic: Use
actions/checkout,actions/setup-node, andactions/cacheonly. Core enforcement logic is native shell/Node — never a third-party action. - Coverage gate must be server-enforced: The coverage threshold check must be in CI, not only in local hooks.
- Composite Actions for reuse: Shared enforcement logic (e.g., "run tests + coverage") must be extracted to
.github/actions/<name>/action.yml— not duplicated across workflows.
Workflow
Step 1: Understand the enforcement gap
Ask: "What can a contributor bypass with git push --no-verify or by skipping the pre-commit hook?"
These gaps are what CI must cover.
Step 2: Design the workflow structure
# .github/workflows/ci.yml
name: CI
on:
push:
branches: [main]
pull_request:
jobs:
test:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [18.x, 20.x, 22.x] # Cross-version matrixStep 3: Coverage gate pattern (DiD standard)
- name: Run tests with coverage
run: |
node --test --experimental-test-coverage \
--test-reporter=spec \
tests/*.test.js 2>&1 | tee coverage.txt
- name: Enforce coverage threshold
run: |
node scripts/check-coverage.js coverage.txtStep 4: Composite Action extraction
If the same steps appear in 2+ workflows:
# .github/actions/run-tests/action.yml
name: Run Tests
description: Shared test runner with coverage gate
runs:
using: composite
steps:
- run: npm ci
shell: bash
- run: npm test
shell: bashStep 5: Verify server-side enforcement
- Open a PR with a known-failing test
- Confirm CI blocks the merge (not just warns)
- Confirm the failure message names the specific test/guard that failed
DiD-Specific CI Architecture
| Workflow | Trigger | Purpose |
ci.yml | push + PR | Test suite + coverage gate |
security.yml | push + PR + schedule | npm audit + CodeQL |
Composite: run-tests | shared | Node version matrix + coverage |
Output Contract
| File | Purpose |
.github/workflows/<name>.yml | Workflow definition |
.github/actions/<name>/action.yml | Reusable composite (if applicable) |
scripts/check-coverage.js | Coverage threshold enforcement |
Anti-Patterns
- Third-party coverage actions —
codecov/codecov-actionintroduces an external dependency. DiD uses native Node coverage parsing. continue-on-error: trueon enforcement steps — This converts a gate into a suggestion. Never use on coverage or test steps.- Hardcoded Node version — Always use a matrix. DiD guarantees cross-version compatibility.
- Missing
npm ci— Always usenpm ci(notnpm install) in CI for reproducible installs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

