stand-ci
Skill1 starsChanged 11 days agoMITView on GitHub
CI/CD and GitHub Actions guidelines. Use when writing workflows or Actions. Shell script code must be in dedicated .sh or .py files. Actions must be pinned to SHAs, not versions.
- Installs packages
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- branchSkill
- coderabbitSkill
- commitSkill
- greptileSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- raycastSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- stand-tsSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- testSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- turbo-verifySkill
- which-prSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Add version as comment for readability
- Distinctive: line 86
Follow shell script best practices (set -euo pipefail for bash)
- Distinctive: line 90
If CI needs to verify that two files agree on the same value, the second file is a derived artifact — generate it, don't validate it.
- Very specific: line 100
Treat automation hooks as convenience, not correctness.
≈ “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
CI/CD Standards
Standards for CI/CD pipelines and GitHub Actions.
GitHub Actions / Workflows
- Shell script code should NOT be inline in Actions/Workflow YAML files
- Extract scripts to dedicated
.shor.pyfiles in ascripts/directory - Reference these scripts from the workflow
- ALWAYS pin actions to full commit SHAs, NOT version tags
Action Pinning
Actions MUST be pinned to SHA hashes for security and reproducibility:
# WRONG - version tag (can be moved, vulnerable to supply chain attacks)
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
# CORRECT - pinned to SHA (immutable, secure)
- uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- uses: actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c # v5.0.0Finding SHAs
- Go to the action's releases page
- Click on the version tag
- Copy the full commit SHA
- Add version as comment for readability
Why
- Easier to test scripts locally
- Better syntax highlighting and linting
- Reusable across workflows
- Cleaner workflow files
- Proper version control diffs
Examples
# WRONG - inline script in workflow
jobs:
build:
steps:
- name: Build and deploy
run: |
echo "Building..."
npm install
npm run build
if [ -f dist/index.js ]; then
aws s3 sync dist/ s3://bucket/
fi
# CORRECT - reference external script
jobs:
build:
steps:
- name: Build and deploy
run: ./scripts/ci/build-and-deploy.shScript Organization
scripts/
└── ci/
├── build.sh
├── deploy.sh
├── test.sh
└── utils/
└── helpers.pyScript Requirements
- Scripts must be executable (
chmod +x) - Include shebang line (
#!/usr/bin/env bashor#!/usr/bin/env python3) - Follow shell script best practices (set -euo pipefail for bash)
No Hand-Maintained Mirrors of Canonical Sources
If CI needs to verify that two files agree on the same value, the second file is a derived artifact — generate it, don't validate it.
- Replace
verify-X-sync.pyscripts withgenerate-X.py; CI runs the generator with--check(exit 1 + unified diff on drift) instead of parsing both files and comparing. - The same generator runs locally for the writer flow and in CI for the gate flow — a single code path, no parser duplication.
- Generators consumed by automation (e.g. Renovate
postUpgradeTasks) should be stdlib-only so they run in any minimal container without dep installation. - Treat automation hooks as convenience, not correctness. The
--checkgate is the truth-keeper; if the hook silently fails, CI still catches the drift.
# WRONG — verify two files agree
- run: python3 scripts/ci/verify-manifest-sync.py
- run: python3 scripts/ci/verify-tool-version-sync.py
# CORRECT — single generator, single check
- run: python3 scripts/ci/generate-tool-versions.py --checkDoes 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.

