본문으로 건너뛰기
cccskills
무료GitHub에 공개

github-codespaces-efficiency

Audit GitHub Codespaces startup time and spending, then identify up to three evidence-based improvements to development containers, machine sizes, prebuilds, or idle timeouts, with validation results and expected impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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 branches with sustained usage.

연동 도구GitHub
설치 방법 보기

이럴 때 유용합니다

  • Investigating slow Codespaces startup
  • Reviewing Codespaces spending
  • Trimming unused development container components
  • Tuning prebuild scope and idle timeouts

포함된 파일(3)

  • SKILL.md4.6 KB
  • references/codespaces.md2.1 KB
  • references/review-rubric.md467 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

GitHub Codespaces Efficiency

Use this skill as a lean entrypoint for GitHub Codespaces efficiency work. Inspect the repo, identify waste, and load only needed references.

If no .devcontainer/ exists yet, load references/codespaces.md and define a baseline before proceeding with the steps below.

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.
  • The user is setting up Codespaces for the first time or needs help creating a new .devcontainer/ from scratch.

Load Only What You Need

Core Workflow

1. Measure first

find .devcontainer -maxdepth 2 -type f
gh codespace list
repo=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
gh api "/repos/$repo/codespaces/machines"

If gh auth fails or the user lacks repo admin scope, proceed with static analysis of .devcontainer/ files; mark machine-type and prebuild recommendations as unverified.

Look for: devcontainer image >2 GB or more than 10 features, machine type larger than usage data supports, missing devcontainer-lock.json (recommend adding — many repos predate lock-file support), prebuilds scoped too broadly, and idle timeout mismatched to usage patterns.

2. Apply guardrails

Check each proposed fix against these rules before recommending it:

  1. Does not remove tools the team uses every day — drop any fix that strips required development tools or extensions.
  2. Does not assume smaller is always better — balance machine cost against developer experience and throughput.
  3. Does not turn the devcontainer into a production image — drop any fix that adds production-only dependencies unless the team explicitly requires it.
  4. Incremental changes preferred — a greenfield baseline is appropriate only when no .devcontainer/ exists; flag (do not drop) changes that restructure an existing config.
  5. Repo changes stay separate from org settings — split any fix that mixes repo-editable files with org-level or user-level Codespaces settings into two distinct recommendations.

3. Select the top 3 fixes

From the six candidates below, keep only those supported by audit evidence from step 1 and passing all guardrails from step 2. Rank survivors by estimated monthly cost savings (USD). Select all candidates that meet both criteria, up to a maximum of 3.

  1. Trim devcontainer — remove features, packages, or extensions not needed for everyday development work; target image <2 GB and fewer than 10 features
  2. Right-size machine type — match to observed usage patterns; if data is unavailable, state assumptions explicitly
  3. Scope prebuilds — enable for the default branch, release/* branches active in the last 14 days, and branches with more than 5 Codespaces per week; disable for all others
  4. Tune idle timeout — 30 min default; 15 min if most sessions end before 30 min; 60 min if most sessions run longer
  5. Remove unused extensions or port-forwarding rules
  6. Reduce devcontainer image size and improve layer caching

4. Verify

  • Start a test Codespace to confirm devcontainer changes build and start as expected.
  • Validate machine sizing against observed usage when telemetry is available; otherwise mark as unverified.
  • Treat unexpected build or startup failures as real bugs even when the configuration looks correct.

Required Output

Waste sources: [top cost or startup-time drivers]

Proposed fixes: [top 3 changes supported by audit evidence and passing guardrails]

Validation: [proven live / static-only / remaining risk]

Impact:

  • Startup time: [expected] / [measured if available]
  • Monthly spend: [expected] / [measured if available]
  • Resource utilization: [expected] / [measured if available]

References

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot4만2026년 10월 17일 업데이트

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot4만2026년 10월 17일 업데이트

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot4만2026년 10월 17일 업데이트

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot4만2026년 10월 17일 업데이트

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot4만2026년 10월 17일 업데이트

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot4만2026년 10월 17일 업데이트

github의 스킬 모두 보기

이 스킬의 문제 신고