メニュー
Porting changes from the legacy shopsys/deployment package (upstream PRs, manifest fixes) into these charts. Use when asked to review/port upstream deployment PRs or to check what changed upstream.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/shopsys/helm --skill sync-upstream-deploymentコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Fan-out code review of multiple/all open PRs - one parallel worktree-isolated agent per PR, each following the review-pr skill protocol, then cross-PR verification, cleanup and summary. Use when asked to review all open PRs or several PRs at once; a single PR needs only review-pr.
Detailed code review of ONE pull request - scope vs its (possibly stacked) base, verification-first findings (render + tests + web research), posting a GitHub review with anchored inline comments signed "Claude Agent (CR)". Use when asked to review a specific PR; for all open PRs at once use review-open-prs, which fans this out.
Conventions for creating GitHub issues in this repository - body structure, title prefixes, the label taxonomy and cross-linking rules. Use whenever filing new issues or turning analysis/review findings into backlog items.
SKILL.md を表示中
| name | sync-upstream-deployment |
| description | Porting changes from the legacy shopsys/deployment package (upstream PRs, manifest fixes) into these charts. Use when asked to review/port upstream deployment PRs or to check what changed upstream. |
This package replaced github.com/shopsys/deployment, but the legacy repo still receives PRs (often by the same maintainer) until every project migrates. Changes flow one way: legacy → here.
gh pr list -R shopsys/deployment --state open --json number,title
gh pr view <N> -R shopsys/deployment --json title,body,files
gh pr diff <N> -R shopsys/deployment | awk '/^diff --git/{f=$3; show=(f !~ /expected|UPGRADE|README/)} show'
Skip tests/scenarios/*/expected/* (legacy snapshots), UPGRADE.md, README.md — the
substance is in kubernetes/*.yaml and deploy/*.sh.
| Legacy | Here |
|---|---|
manifest edit in kubernetes/ | chart template + values default |
deploy/parts/*.sh logic (sed/yq at deploy time) | values/env overlay, helper, or helmfile mechanism |
| new env variable | committed value; env interpolation in runtime.yaml.gotmpl only if sensitive/CI-dynamic |
| kubectl exec / imperative step | helm hook Job or wrapper step (last resort) |
| new kustomize resource | new template (+ schema + docs) |
Check first whether the change is already covered — by the phase-1 port itself, an existing
issue (search the tracker), or an intentional deviation
(docs/migrating-from-shopsys-deployment.md).
shopsys/deployment#N in commit/PR/deviations entry)create-issue skill); if an issue already covers the topic, add the spec as a commenttools/compare-legacy.sh semantically diffs our render against the legacy snapshots:
LEGACY_REPO=/path/to/shopsys-deployment ./tools/compare-legacy.sh <scenario>
It canonicalizes both sides (sorted keys, sorted env, stripped hook/checksum noise). Expect
the documented deviations to show up; anything else is a finding. Note yq-v4 artifacts:
0644-style octals display as decimal (YAML 1.1 vs 1.2) — cosmetic only.