“helm”的搜索结果

DBマイグレーション作成時に使用。バージョン番号競合防止。mainブランチ確認必須。

中文简介正在准备中。当前显示原文说明。

Use when continuing implementation from an existing plan

中文简介正在准备中。当前显示原文说明。

Use when verified implementation is ready for an integration decision or authorized integration

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

変更内容からミューテーション/E2Eの推奨度を判定し、強く推奨・範囲が小さい・副作用なしのものは確認なしで実施し、それ以外は最後の報告で確認する。quality-check Step 5から参照実行されるほか、開発中の任意タイミングで単体実行できる。

中文简介正在准备中。当前显示原文说明。

Use when arranging the project quality-check or investigating a concrete unresolved code concern

中文简介正在准备中。当前显示原文说明。

Use when independent bounded tasks benefit from delegation during implementation

中文简介正在准备中。当前显示原文说明。

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

中文简介正在准备中。当前显示原文说明。

Use when implementing any feature or bugfix, before writing implementation code

中文简介正在准备中。当前显示原文说明。

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

中文简介正在准备中。当前显示原文说明。

Use when selecting skills for a task or resolving how skill workflows apply

中文简介正在准备中。当前显示原文说明。

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

中文简介正在准备中。当前显示原文说明。

Use before implementing any feature, behavior change, or refactor - settles requirements and design, then gets the design independently reviewed and approved by the user before code is written

中文简介正在准备中。当前显示原文说明。

Git worktree を使った並列開発時に使用。配置・ポート割当・環境コピー・クリーンアップを標準化する。

中文简介正在准备中。当前显示原文说明。

Use when a multi-step change needs explicit sequencing, dependencies, or a handoff

中文简介正在准备中。当前显示原文说明。

Use when creating new skills, editing existing skills, or verifying skills work before deployment

中文简介正在准备中。当前显示原文说明。

Use when user shows signs of overwhelm or frustration — repeated failed attempts, tone shifts, sudden brevity, topic abandonment. Guides gentle check-ins without being patronizing or clinical.

中文简介正在准备中。当前显示原文说明。

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

中文简介正在准备中。当前显示原文说明。

Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use data-pipeline-engineer), API design (use api-architect).

中文简介正在准备中。当前显示原文说明。

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

中文简介正在准备中。当前显示原文说明。

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

中文简介正在准备中。当前显示原文说明。

Triage ASM/recon output for ownership before testing — separate the target's real assets from namespace-collision noise. Automated recon keyword-matches on the brand name, so for any target whose name is a common/dictionary word, the output is dominated by assets belonging to UNRELATED same-named companies (repos, cloud buckets, mobile apps, breach corpora, typosquats). Built from an authorized engagement where an ASM report's 'Criticals' were overwhelmingly false positives and the combo/repos/mobile/bucket lists were polluted with unrelated same-named orgs. Use at the START of any engagement, immediately on receiving any ASM/recon/OSINT dataset, BEFORE testing anything.

中文简介正在准备中。当前显示原文说明。

Hunt Kubernetes & Docker — API anonymous access, kubelet 10250 exec (SPDY/WebSocket, NOT plain POST) and the simpler /run primitive, etcd 2379 unauth, dashboard skip-login, RBAC misconfig, secret/SA-token abuse, docker.sock host escape, runc/container-escape (Leaky Vessels CVE-2024-21626), API-server-mediated nodes/proxy RCE, EphemeralContainers node-shell, bound/projected SA-token audience+expiry abuse, admission-controller bypass, Helm/Tiller remnants. Use when target runs containerized infra, exposes K8s ports (6443/10250/10255/2379/8443), or cloud metadata reveals K8s service accounts.

中文简介正在准备中。当前显示原文说明。