github/awesome-copilot / skills/github-actions-efficiency
github-actions-efficiency
UnverifiedAudit GitHub Actions workflow efficiency and recommend fixes to reduce CI minutes and costs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.5 KB |
| references/actions.md | markdown | 3.1 KB |
| references/patterns.md | markdown | 1.3 KB |
| references/reporting.md | markdown | 1.5 KB |
| references/review-rubric.md | markdown | 465 B |
references/reporting.md
View on GitHub# Efficiency Reporting and Follow-Up Review
Load this reference when the user asks what changed, wants a before/after report, or asks for another pass over remaining expensive jobs.
## Reporting Rules
- Separate expected savings from measured savings.
- Do not claim exact time or cost savings without before/after run data.
- Call out confounders such as cache warm-up, changed matrix breadth, runner changes, or unusually small PRs.
Use this phrasing when data is incomplete:
`I can report the efficiency mechanisms that changed, but I cannot honestly claim exact minutes saved without comparing before/after GitHub Actions runs.`
## What To Measure
Gather:
1. A baseline sample before the change
2. A post-change sample after caches warm
3. Per-workflow or per-job duration comparisons
4. Avoided runs, skipped jobs, or avoided matrix legs
Always separate:
- PR wall-clock time
- Total runner time across jobs
- Work avoided entirely
These answer different questions. A change can reduce runner spend without materially improving the fastest feedback path.
## Follow-Up Review Pass
After the first round of fixes is validated, inspect the remaining expensive jobs:
- Compare setup time versus execution time
- Identify heavyweight wrapper actions and confirm what they really enforce
- Review whether each matrix dimension still serves an active decision
- Recheck after caches warm
- Break down the dominant slow step before proposing further changes
Keep the follow-up compact. Report the next few highest-value opportunities, not a long wishlist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |