split skill into 2 and applied further context saving by moving reporting into refeences

Author: Mark Heynes

docs/README.skills.md

@@ -177,7 +177,8 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [geofeed-tuner](../skills/geofeed-tuner/SKILL.md)<br />`gh skills install github/awesome-copilot geofeed-tuner` | Use this skill whenever the user mentions IP geolocation feeds, RFC 8805, geofeeds, or wants help creating, tuning, validating, or publishing a self-published IP geolocation feed in CSV format. Intended user audience is a network operator, ISP, mobile carrier, cloud provider, hosting company, IXP, or satellite provider asking about IP geolocation accuracy, or geofeed authoring best practices. Helps create, refine, and improve CSV-format IP geolocation feeds with opinionated recommendations beyond RFC 8805 compliance. Do NOT use for private or internal IP address management — applies only to publicly routable IP addresses. | `assets/example`<br />`assets/iso3166-1.json`<br />`assets/iso3166-2.json`<br />`assets/small-territories.json`<br />`references/rfc8805.txt`<br />`references/snippets-python3.md`<br />`scripts/templates` |
 | [git-commit](../skills/git-commit/SKILL.md)<br />`gh skills install github/awesome-copilot git-commit` | Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping | None |
 | [git-flow-branch-creator](../skills/git-flow-branch-creator/SKILL.md)<br />`gh skills install github/awesome-copilot git-flow-branch-creator` | Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model. | None |
-| [github-actions-codespaces-efficiency](../skills/github-actions-codespaces-efficiency/SKILL.md)<br />`gh skills install github/awesome-copilot github-actions-codespaces-efficiency` | Audit and improve GitHub Actions and Codespaces efficiency. Use this skill when a user wants to reduce CI minutes, cancel redundant runs, add dependency caching, narrow workflow triggers with path filters, slim devcontainers, right-size Codespaces, tune idle timeout guidance, or scope prebuilds to high-value branches. | `references/actions.md`<br />`references/codespaces.md`<br />`references/patterns.md`<br />`references/reporting.md` |
+| [github-actions-efficiency](../skills/github-actions-efficiency/SKILL.md)<br />`gh skills install github/awesome-copilot github-actions-efficiency` | Audit and improve GitHub Actions workflow efficiency. Use this skill when a user wants to reduce CI minutes, cancel redundant runs, add dependency caching, narrow workflow triggers with path filters, reduce matrix breadth, or optimize job parallelism. | `references/actions.md`<br />`references/patterns.md`<br />`references/reporting.md`<br />`references/review-rubric.md` |
+| [github-codespaces-efficiency](../skills/github-codespaces-efficiency/SKILL.md)<br />`gh skills install github/awesome-copilot github-codespaces-efficiency` | Audit and improve GitHub Codespaces efficiency. Use this skill when a user wants faster Codespaces startup, lower Codespaces spend, slim devcontainers, right-size machines, tune idle timeout, or scope prebuilds to high-value branches. | `references/codespaces.md`<br />`references/review-rubric.md` |
 | [github-copilot-starter](../skills/github-copilot-starter/SKILL.md)<br />`gh skills install github/awesome-copilot github-copilot-starter` | Set up complete GitHub Copilot configuration for a new project based on technology stack | None |
 | [github-issues](../skills/github-issues/SKILL.md)<br />`gh skills install github/awesome-copilot github-issues` | Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task. | `references/dependencies.md`<br />`references/images.md`<br />`references/issue-fields.md`<br />`references/issue-types.md`<br />`references/projects.md`<br />`references/search.md`<br />`references/sub-issues.md`<br />`references/templates.md` |
 | [github-release](../skills/github-release/SKILL.md)<br />`gh skills install github/awesome-copilot github-release` | Guides IA through releasing a new version of a GitHub library end-to-end.  Handles SemVer versioning and Keep a Changelog formatting automatically. | `references/commit-classification.md`<br />`references/semver-rules.md` |

…b-actions-codespaces-efficiency/SKILL.md skills/github-actions-efficiency/SKILL.mdskills/github-actions-codespaces-efficiency/SKILL.md renamed to skills/github-actions-efficiency/SKILL.md skills/github-actions-codespaces-efficiency/SKILL.md renamed to skills/github-actions-efficiency/SKILL.md

@@ -1,29 +1,27 @@
 ---
-name: github-actions-codespaces-efficiency
-description: 'Audit and improve GitHub Actions and Codespaces efficiency. Use this skill when a user wants to reduce CI minutes, cancel redundant runs, add dependency caching, narrow workflow triggers with path filters, slim devcontainers, right-size Codespaces, tune idle timeout guidance, or scope prebuilds to high-value branches.'
+name: github-actions-efficiency
+description: 'Audit and improve GitHub Actions workflow efficiency. Use this skill when a user wants to reduce CI minutes, cancel redundant runs, add dependency caching, narrow workflow triggers with path filters, reduce matrix breadth, or optimize job parallelism.'
 ---
 
-# GitHub Actions and Codespaces Efficiency
+# GitHub Actions Efficiency
 
-Use this skill as a lean entrypoint for GitHub Actions and Codespaces efficiency work. Keep the hot path small: inspect the repo, identify the waste source, then load only the reference material needed for the current task.
+Use this skill as a lean entrypoint for GitHub Actions efficiency work. Keep the hot path small: inspect the repo, identify the waste source, then load only the reference material needed for the current task.
 
 ## Use This Skill When
 
 - The user wants to reduce GitHub Actions runtime, CI cost, or wasted workflow runs.
-- The user wants faster Codespaces startup or lower Codespaces spend.
-- The repo has `.github/workflows/*.yml`, a `.devcontainer/`, or explicit Codespaces configuration questions.
-- The user asks for caching, concurrency, path filters, matrix reduction, prebuild strategy, machine sizing, or idle-timeout guidance.
+- The repo has `.github/workflows/*.yml` and explicit GitHub Actions configuration questions.
+- The user asks for caching, concurrency, path filters, matrix reduction, job optimization, or workflow-specific fixes.
 
 ## Load Only What You Need
 
 Start with the repo configuration, then load references selectively:
 
 - Read [`references/actions.md`](./references/actions.md) for GitHub Actions audits, job gating, matrix reduction, live validation, and workflow-specific fixes.
-- Read [`references/codespaces.md`](./references/codespaces.md) for devcontainer, machine-sizing, prebuild, and idle-timeout guidance.
 - Read [`references/reporting.md`](./references/reporting.md) when the user asks what changed, wants a before/after efficiency report, or wants another review pass over the remaining expensive jobs.
 - Read [`references/patterns.md`](./references/patterns.md) only when you need concrete YAML or configuration examples during implementation.
 
-If the task is CI-only, do not load the Codespaces reference. If the task is Codespaces-only, do not load the Actions reference.
+If the task is Codespaces-related, use the `github-codespaces-efficiency` skill instead.
 
 ## Core Workflow
 
@@ -35,15 +33,14 @@ Inspect the current configuration before proposing changes:
 - Dependency installation and cache behavior
 - Whether docs-only or config-only changes trigger heavy validation
 - Whether matrix breadth matches the actual decision being made
-- Whether devcontainers or Codespaces defaults are oversized
+- Job parallelism and critical path analysis
 
 Start with a compact repo audit like this:
 
 ```bash
-rg -n "on:|concurrency:|paths:|paths-ignore:|strategy:|matrix:|cache:" .github/workflows .devcontainer
+rg -n "on:|concurrency:|paths:|paths-ignore:|strategy:|matrix:|cache:" .github/workflows
 gh run list --limit 10
 gh run view --log-failed
-find .devcontainer -maxdepth 2 -type f
 ```
 
 ### 2. Rank fixes by payoff
@@ -55,7 +52,7 @@ Prefer this order unless repo context says otherwise:
 3. Remove duplicate workflow coverage before merging jobs together
 4. Narrow workflow or job triggers safely
 5. Reduce matrix breadth to match risk and event type
-6. Trim oversized devcontainer or Codespaces defaults
+6. Optimize job parallelism while preserving critical path
 
 ### 3. Keep changes conservative
 
@@ -88,20 +85,9 @@ For measured impact, separate:
 - Total runner time across jobs
 - Jobs or matrix legs avoided entirely
 
-## Review Rubric
-
-Use this rubric when reviewing current or updated efficiency work:
-
-- `Scope discipline`: only relevant domain guidance was loaded
-- `Safety`: required validation coverage was preserved
-- `Token efficiency`: the skill or report stayed focused on the active task
-- `Measurement quality`: expected and measured gains were clearly separated
-
-If one rubric dimension is weak, call that out explicitly instead of averaging it away.
-
 ## References
 
 - [`references/actions.md`](./references/actions.md)
-- [`references/codespaces.md`](./references/codespaces.md)
 - [`references/reporting.md`](./references/reporting.md)
 - [`references/patterns.md`](./references/patterns.md)
+- [`references/review-rubric.md`](./references/review-rubric.md) — load when reviewing completed efficiency work

…espaces-efficiency/references/actions.md …actions-efficiency/references/actions.mdskills/github-actions-codespaces-efficiency/references/actions.md renamed to skills/github-actions-efficiency/references/actions.md skills/github-actions-codespaces-efficiency/references/actions.md renamed to skills/github-actions-efficiency/references/actions.md

@@ -0,0 +1,12 @@
+# Review Rubric
+
+Load this reference when reviewing current or updated efficiency work.
+
+Use this rubric:
+
+- `Scope discipline`: only GitHub Actions guidance was loaded
+- `Safety`: required validation coverage was preserved
+- `Token efficiency`: the skill or report stayed focused on the active task
+- `Measurement quality`: expected and measured gains were clearly separated
+
+If one rubric dimension is weak, call that out explicitly instead of averaging it away.

…spaces-efficiency/references/patterns.md …ctions-efficiency/references/patterns.mdskills/github-actions-codespaces-efficiency/references/patterns.md renamed to skills/github-actions-efficiency/references/patterns.md skills/github-actions-codespaces-efficiency/references/patterns.md renamed to skills/github-actions-efficiency/references/patterns.md

@@ -0,0 +1,89 @@
+---
+name: github-codespaces-efficiency
+description: 'Audit and improve GitHub Codespaces efficiency. Use this skill when a user wants faster Codespaces startup, lower Codespaces spend, slim devcontainers, right-size machines, tune idle timeout, or scope prebuilds to high-value branches.'
+---
+
+# GitHub Codespaces Efficiency
+
+Use this skill as a lean entrypoint for GitHub Codespaces efficiency work. Keep the hot path small: inspect the repo, identify the waste source, then load only the reference material needed for the current task.
+
+## Use This Skill When
+
+- The user wants faster Codespaces startup or lower Codespaces spend.
+- The repo has a `.devcontainer/` or explicit Codespaces configuration questions.
+- The user asks for devcontainer optimization, machine sizing, prebuild strategy, or idle-timeout guidance.
+
+## Load Only What You Need
+
+Start with the repo configuration, then load references selectively:
+
+- Read [`references/codespaces.md`](./references/codespaces.md) for devcontainer, machine-sizing, prebuild, idle-timeout guidance, and reporting.
+
+If the task is GitHub Actions-related, use the `github-actions-efficiency` skill instead.
+
+## Core Workflow
+
+### 1. Measure first
+
+Inspect the current configuration before proposing changes:
+
+- Whether devcontainers or Codespaces defaults are oversized
+- Machine type selection and whether it matches actual development needs
+- Prebuild configuration and which branches have prebuilds enabled
+- Idle timeout settings and usage patterns
+- Extension and port forwarding overhead
+
+Start with a compact repo audit like this:
+
+```bash
+find .devcontainer -maxdepth 2 -type f
+gh codespace list
+gh api /repos/{owner}/{repo}/codespaces/new?machine=machine-name
+```
+
+### 2. Rank fixes by payoff
+
+Prefer this order unless repo context says otherwise:
+
+1. Trim oversized devcontainer or Codespaces defaults
+2. Right-size machine types based on actual usage patterns
+3. Configure prebuilds for high-value branches only
+4. Tune idle timeout to match development habits
+5. Remove unnecessary extensions or port forwards
+6. Optimize devcontainer image size and layer caching
+
+### 3. Keep changes conservative
+
+- Do not remove required development tools or extensions that are essential for the workflow.
+- Do not assume smaller machines always mean better productivity; balance cost with developer experience.
+- Treat prebuild configuration as a trade-off between storage cost and startup time.
+- Prefer incremental changes over complete devcontainer rewrites.
+- Separate repo-editable changes from GitHub/org settings recommendations.
+
+### 4. Verify in GitHub when possible
+
+Configuration changes should be tested when possible.
+
+- Validate machine sizing by monitoring actual resource usage.
+- Use a test Codespace to verify devcontainer changes work as expected.
+- Treat unexpected behavior as a real bug even when the configuration looks correct.
+
+## Required Output Shape
+
+When using this skill, keep the response compact and structured around these four sections:
+
+1. `Waste sources`: the top cost or latency drivers you found
+2. `Proposed fixes`: the small set of highest-confidence changes
+3. `Validation`: what was proven live, what was only checked locally, and any remaining risk
+4. `Impact`: expected savings separately from measured savings
+
+For measured impact, separate:
+
+- Codespace startup time
+- Monthly spend reduction
+- Resource utilization improvement
+
+## References
+
+- [`references/codespaces.md`](./references/codespaces.md)
+- [`references/review-rubric.md`](./references/review-rubric.md) — load when reviewing completed efficiency work

…paces-efficiency/references/reporting.md …tions-efficiency/references/reporting.mdskills/github-actions-codespaces-efficiency/references/reporting.md renamed to skills/github-actions-efficiency/references/reporting.md skills/github-actions-codespaces-efficiency/references/reporting.md renamed to skills/github-actions-efficiency/references/reporting.md

@@ -0,0 +1,12 @@
+# Review Rubric
+
+Load this reference when reviewing current or updated efficiency work.
+
+Use this rubric:
+
+- `Scope discipline`: only Codespaces guidance was loaded
+- `Safety`: required development capabilities were preserved
+- `Token efficiency`: the skill or report stayed focused on the active task
+- `Measurement quality`: expected and measured gains were clearly separated
+
+If one rubric dimension is weak, call that out explicitly instead of averaging it away.