メニュー
Back-sync an environment branch down the deploy chain (hotfix propagation) on demand
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
This skill should be used to drive a pull request all the way to MERGED, handling ANYTHING that blocks the merge. It enables auto-merge when the repo supports it (direct-merge fallback otherwise), keeps the branch rebased/synced and resolves merge conflicts, fixes failing CI/deploy checks, addresses and resolves every human and bot review comment (CodeRabbit, etc.) — implementing valid feedback and replying-then-resolving invalid feedback — dismisses stale CHANGES_REQUESTED gates, and verifies the fix actually shipped (auto-merge race ancestry check). Composable and inline — invoked by other skills (e.g. git-submit-pr, implement, sync-down) via the Skill tool, never as a standalone user command.
Address and resolve PR review comments (human + bot): implement valid feedback, reply to invalid, resolve every thread.
This skill should be used to address and resolve the code review feedback on a pull request — human and bot (CodeRabbit, etc.). It fetches every unresolved review thread with its resolution state via GraphQL, triages each one, implements valid feedback (commit + push), replies to invalid/not-applicable feedback explaining why, and resolves every handled thread via the GraphQL resolveReviewThread mutation so branch-protection thread-resolution gates clear. Composable and chainable — runnable standalone via /lisa:pull-request:review or invoked inline by other skills (drive-pr-to-merge, verify) via the Skill tool.
SOC 職業分類に基づく
| name | lisa-sync-down |
| description | Back-sync an environment branch down the deploy chain (hotfix propagation) on demand |
/lisa:sync-down$lisa-sync-down or a plain-English request that matches this skill.[source-env-or-branch]Skill. Codex tool access is governed by the active Codex runtime and project policy.Use the /lisa:sync-down skill to back-sync an environment branch down the deploy chain — deriving the source→target chain from .lisa.config.json deploy.order + deploy.branches, then merging, resolving conflicts, opening PRs, and enabling auto-merge for each downward hop. Use the user's surrounding request as this command's arguments.