github-workflows
Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.
- License 许可
- MIT
- 所属仓库
- open-gsd/gsd-pi
- 最近更新
- 2026-11-15
- Stars
- ★ 1.4k
- Forks
- 118
01 前言 Front Matter
- name
- github-workflows
- description
- Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.
03 SKILL.md 正文
GitHub Workflows
Mission: Work with GitHub Actions without using stale training data. All syntax, versions, and parameters come from live sources.
Structural Principle
All CI operations go through ci_monitor.cjs. Never reach for gh CLI directly — the script wraps it with observable output.
Primary Tool: ci_monitor.cjs
Path: scripts/ci_monitor.cjs
node scripts/ci_monitor.cjs <command>
Before using any command:
- [ ] Run
--helpto discover available arguments
Routing Table:
| When You Need | Command |
|---|---|
| List recent runs | runs [--branch <name>] |
| Monitor running workflow | watch <run-id> |
| Fail fast in scripts | fail-fast <run-id> |
| See why run failed | log-failed <run-id> |
| Test pass/fail counts | test-summary <run-id> |
| Check action versions | check-actions [file] |
| Search logs | grep <run-id> --pattern <regex> |
| Wait for deployment | wait-for <run-id> <job> --keyword <text> |
Documentation Routing
Base URL: https://docs.github.com/en/actions/reference/workflows-and-actions/
Before writing any workflow syntax:
- [ ] Fetch the relevant
.mdfile from the URL above - [ ] Read only the section you need
| Task | File | Section |
|---|---|---|
| Create workflow | workflow-syntax.md | name, on, jobs |
| Set triggers | workflow-syntax.md | on |
| Set permissions | workflow-syntax.md | permissions |
| Concurrency | workflow-syntax.md | concurrency |
| Reusable workflow | workflow-syntax.md | on.workflow_call |
| Annotations | workflow-commands.md | "Setting an error/warning/notice message" |
| Output variables | workflow-commands.md | "Environment files" |
| Conditionals | expressions.md | "Operators", "Functions" |
| Contexts | contexts.md | "<context> context" |
| Events | events-that-trigger-workflows.md | Event tables |
Version Verification
| What | Where |
|---|---|
| Action versions | node ci_monitor.cjs check-actions <file> |
| Node.js LTS | curl -s https://nodejs.org/dist/index.json | jq '.[0].version' |
Validation Constraint
"No errors" is not validation. Prove observable change:
BEFORE: [specific state]
AFTER: [different state]
EVIDENCE: [output from ci_monitor.cjs]
References
references/gh/SKILL.md— gh CLI reference
04 同仓库更多 Skills
write-milestone-brief
Synthesize the current conversation into a milestone brief (PRD). Saves it as the milestone CONTEXT (`gsd_summary_save`) by default, or files a GitHub issue only with explicit user confirmation. Use when asked to "turn this into a PRD", "draft a milestone brief", "capture this context", "write it up", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.
write-docs
Collaborative authoring workflow for proposals, technical specs, decision docs, READMEs, ADRs, and long-form prose that must work for fresh readers. Three stages: gather context, iterate on structure, reader-test for a stranger. Use when asked to "write the docs", "draft a proposal", "write a spec", "write an RFC", "write the README", or when a doc must be understandable without this session's context.
web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
verify-before-complete
Block completion claims until verification evidence has been produced in the current message. Use before marking a task/slice/milestone complete, before creating a commit or PR, before saying "it works" or "tests pass", and any time you are about to claim work is done. The rule is: evidence before claims, always — running the verification must happen now, not "earlier in the session". Fresh output or no claim.
userinterface-wiki
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.