copilot_dev/.github/skills/engineering/tooling/helm-cli/SKILL.md
# Helm CLI Cheatsheet (Operational) ## When to use - You need fast, correct Helm commands (install/upgrade/status/history/rollback) - You want deterministic chart rendering and debugging ## Workflow 1) Inspect releases - `helm list -A` - `helm status <release> -n <ns>` - `helm history <release> -n <ns>` 2) Get rendered state - `helm get manifest <release> -n <ns>` - `helm get values <release> -n <ns> -a` 3) Render locally (debug) - `helm lint <chartDir>` - `helm template
npx skillsauth add nist0/copilotdev-tmp-consumer copilot_dev/.github/skills/engineering/tooling/helm-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
helm list -Ahelm status <release> -n <ns>helm history <release> -n <ns>helm get manifest <release> -n <ns>helm get values <release> -n <ns> -ahelm lint <chartDir>helm template <release> <chartDir> -n <ns> -f values.yaml --debug > rendered.yamlhelm upgrade --install <release> <chartDir> -n <ns> -f values.yaml --wait --timeout 10m--atomic (rolls back on failure)helm rollback <release> <rev> -n <ns> --wait --timeout 10mhelm diff upgrade <release> <chartDir> -n <ns> -f values.yamltools
# Tech Watch (Weekly Digest) ## When to use - You want a weekly digest on selected topics (dotnet, k8s/aks, observability, security, LLM tooling). ## Workflow 1) Define topics and priority order. 2) Collect primary sources (release notes, official docs, papers). 3) Summarize: what changed + why it matters. 4) Propose 1–3 experiments to try next week. ## Outputs - Weekly digest (Markdown) - Experiments list (1–3) with expected payoff - Source list (primary preferred)
development
# Innovation Sprint ## When to use - You need new ideas or alternative designs. - You want a short, structured ideation session. ## Workflow 1) Clarify constraints and success criteria. 2) Generate 8–12 ideas quickly (no filtering). 3) Cluster similar ideas and pick top 3. 4) For top 3: define value, feasibility, risks, and a 1–2h spike plan. ## Outputs - Idea list - Top 3 shortlist + tradeoffs - Spike plan for each shortlisted idea
tools
# VS Code (Copilot Dev Framework Usage) ## When to use - You need to ensure Copilot Dev Framework is loaded correctly in VS Code. - You want best practices for working with prompts, agents, and skills. ## Workflow 1) Bootstrap integration - run `copilot_dev/bootstrap/bootstrap.ps1` or `.sh` 2) Reload - Reload window after bootstrap 3) Discoverability - use `/route` to select agent/prompt/skill - verify prompts appear in the slash command list 4) Multi-root workspaces - ensure
tools
# Postman (API Collections) ## When to use - You want repeatable API request collections with environments. - You want to validate API contract behavior manually or in CI. ## Workflow 1) Organize collections by domain 2) Use environments for base URLs and auth tokens 3) Add tests - status code assertions, schema checks where possible 4) Documentation - include examples and descriptions 5) Version control - export collections; keep in repo if required ## Outputs - Collection struct