workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- workflow-automation
- tags
- [ "engineering", "devops", "deploy" ]
- tools
- [ "monograph_query", "monograph_context", "monograph_impact" ]
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- description
- Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
03 SKILL.md 正文
Workflow Automation — Best Practices
Focus
Build and maintain the CI/CD workflow definitions themselves (GitHub Actions or equivalent) — triggers, jobs, matrices, caching — so pipelines are fast, reliable, and self-explanatory.
Best practices
- Trigger workflows precisely (path filters, branch filters) — don't run the full suite on every push when only docs changed.
- Cache dependencies and build artifacts aggressively; a pipeline that reinstalls from scratch every run is wasting both time and money.
- Parallelize independent jobs (lint, unit tests, build) rather than chaining them sequentially when there's no real dependency.
- Set explicit timeouts on every job so a hung step doesn't burn CI minutes for hours.
- Fail fast on the cheapest checks first (lint, type-check) before running expensive ones (integration tests, e2e).
- Keep workflow YAML DRY via reusable/composite workflows instead of copy-pasting the same steps across files.
- Make failures diagnosable from the log alone — name steps clearly, echo context (commit, inputs) before the risky step runs.
Common pitfalls
- Adding more and more steps to "be safe" without ever removing redundant or superseded checks — pipelines that take 20+ minutes because no one prunes them.
- Hardcoding secrets or tokens directly in workflow YAML instead of using the platform's secrets store.
- Retrying flaky steps blindly instead of fixing or quarantining the flaky test/step.
- Broad wildcard triggers (
on: pushwith no path/branch filter) that fire the whole pipeline for irrelevant changes. - Auto-generated workflow "self-healing" that masks real failures instead of surfacing them.
Tools & techniques
- Path/branch filters and matrix builds to scope and parallelize work precisely.
- Dependency and build caching (lockfile-hash-keyed) to cut repeat-run time.
- Reusable workflows / composite actions for shared steps across multiple pipeline files.
- Required status checks + branch protection as the actual enforcement layer, not the workflow's exit code alone.
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.
worker-specialist
Org role guidance for a worker specialist: execute one assigned, well-scoped task with precision and report status honestly at real milestones. Covers confirming done-criteria first, surfacing blockers immediately and sharing intermediate results with peers.