一键在 Manus 中运行任何 Skill

land

星标9

分支0

更新时间2026年5月24日 11:30

Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

kwanpham2195

kwanpham2195/symphony-go

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Land

Goals

Ensure the PR is conflict-free with main.
Keep CI green and fix failures when they occur.
Squash-merge the PR once checks pass.
Do not yield until the PR is merged; keep the loop running unless blocked.

Preconditions

gh CLI is authenticated.
You are on the PR branch with a clean working tree.

Steps

Locate the PR for the current branch.
Run the full gate locally before any push:
```
make check
```
If uncommitted changes exist, commit with the commit skill and push with the push skill.
Check mergeability and conflicts against main.
If conflicts exist, use the pull skill to merge origin/main and resolve, then push skill to publish.
Watch checks until complete:
```
gh pr checks --watch
```
If checks fail, pull logs, fix, commit, push, and re-watch:
```
gh pr checks
gh run view <run-id> --log-failed
```

When all checks are green, squash-merge:

pr_title=$(gh pr view --json title -q .title)
pr_body=$(gh pr view --json body -q .body)
gh pr merge --squash --subject "$pr_title" --body "$pr_body"

Review Handling

Address all review comments before merging (code fix or explicit pushback with rationale).
For each comment: accept, clarify, or push back. State the mode before changing code.
Reply before pushing code changes.

Failure Handling

If checks fail, inspect with gh run view --log-failed, fix locally, commit, push, re-watch.
Use judgment on flaky failures (timeouts on one platform) — may proceed.
If push is rejected, use the pull skill first.
Do not use --force; only --force-with-lease when history was rewritten.

同仓库更多 Skills

同仓库

commit

kwanpham2195/symphony-go

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

2026-05-249

debug

kwanpham2195/symphony-go

Investigate stuck runs and execution failures by tracing Symphony logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

2026-05-249

linear

kwanpham2195/symphony-go

Use Symphony's linear_graphql client tool for raw Linear GraphQL operations such as comment editing, state transitions, and uploads.

2026-05-249

pull

kwanpham2195/symphony-go

Pull latest origin/main into the current branch and resolve merge conflicts. Use when Codex needs to sync a feature branch with origin before pushing.

2026-05-249

push

kwanpham2195/symphony-go

Push current branch to origin and create or update the PR; use when asked to push, publish updates, or create a pull request.

2026-05-249

symphony

kwanpham2195/symphony-go

Set up, configure, run, and troubleshoot symphony-go — an autonomous agent orchestrator that polls Linear issues and runs Codex sessions. Use when the user asks to install symphony, create a WORKFLOW.md, configure Linear integration, start the orchestrator, debug stuck agents, fix failing hooks, tune retry/backoff, set up workspaces, or any task related to running symphony-go in a repository.

2026-05-249

name	land
description	Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

Land

Goals

Ensure the PR is conflict-free with main.
Keep CI green and fix failures when they occur.
Squash-merge the PR once checks pass.
Do not yield until the PR is merged; keep the loop running unless blocked.

Preconditions

gh CLI is authenticated.
You are on the PR branch with a clean working tree.

Steps

Locate the PR for the current branch.
Run the full gate locally before any push:
```
make check
```
If uncommitted changes exist, commit with the commit skill and push with the push skill.
Check mergeability and conflicts against main.
If conflicts exist, use the pull skill to merge origin/main and resolve, then push skill to publish.
Watch checks until complete:
```
gh pr checks --watch
```
If checks fail, pull logs, fix, commit, push, and re-watch:
```
gh pr checks
gh run view <run-id> --log-failed
```

When all checks are green, squash-merge:

pr_title=$(gh pr view --json title -q .title)
pr_body=$(gh pr view --json body -q .body)
gh pr merge --squash --subject "$pr_title" --body "$pr_body"

Review Handling

Address all review comments before merging (code fix or explicit pushback with rationale).
For each comment: accept, clarify, or push back. State the mode before changing code.
Reply before pushing code changes.

Failure Handling

If checks fail, inspect with gh run view --log-failed, fix locally, commit, push, re-watch.
Use judgment on flaky failures (timeouts on one platform) — may proceed.
If push is rejected, use the pull skill first.
Do not use --force; only --force-with-lease when history was rewritten.