github-workflows
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" |
| 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
More from gsd-build/gsd-2
gsd-orchestrator
>
70debug-like-expert
Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.
20frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
16swiftui
SwiftUI apps from scratch through App Store. Full lifecycle - create, debug, test, optimize, ship.
15test
Generate or run tests. Auto-detects test framework, generates comprehensive tests for source files, or runs existing test suites with failure analysis.
4review
Review code changes for security, performance, bugs, and quality. Reviews staged changes, unstaged changes, specific commits, or PR-ready diffs.
4