post-deploy

部署后操作

Stage 3 of the autonomous deployment pipeline. Triggered by the

deployed

label. Reads the PR's changed files, matches them against configured patterns, and runs targeted actions: ECR image rebuilds, config reload verification, smoke tests, or custom scripts.

自主部署流水线的第3阶段。由

deployed

标签触发。读取PR的变更文件，将其与配置的模式进行匹配，并运行针对性操作：ECR镜像重建、配置重载验证、冒烟测试或自定义脚本。

When to Use

使用场景

Triggered by
```
deployed
```
label via event-rules (after deployment-checker confirms live deploy)
Manual:
```
/post-deploy PR_NUMBER org/repo
```

通过事件规则由
```
deployed
```
标签触发（在deployment-checker确认部署上线后）
手动触发：
```
/post-deploy PR_NUMBER org/repo
```

Invocation

调用方式

/post-deploy 42 fellowship-dev/pylot

/post-deploy 42 fellowship-dev/pylot

Runbook

运行手册

Step 0: Dedup Gate

步骤0：重复执行检查 gate

bash

PR=$1
REPO=$2

bash

PR=$1
REPO=$2

Check if post-deploy already ran (look for a post-deploy comment)

EXISTING=$(gh pr view $PR --repo $REPO --json comments
--jq '.comments[].body' | grep "Post-deploy actions" || true) if [ -n "$EXISTING" ]; then echo "[post-deploy] outcome="already complete — post-deploy comment found" status=success" exit 0 fi

undefined

EXISTING=$(gh pr view $PR --repo $REPO --json comments
--jq '.comments[].body' | grep "Post-deploy actions" || true) if [ -n "$EXISTING" ]; then echo "[post-deploy] outcome="already complete — post-deploy comment found" status=success" exit 0 fi

undefined

Step 1: Read PR Context

步骤1：读取PR上下文

bash

PR_DATA=$(gh pr view $PR --repo $REPO --json number,title,url,files,mergeCommit,baseRefName)
PR_TITLE=$(echo "$PR_DATA" | python3 -c "import json,sys; print(json.load(sys.stdin)['title'])")
PR_URL=$(echo "$PR_DATA" | python3 -c "import json,sys; print(json.load(sys.stdin)['url'])")
CHANGED_FILES=$(echo "$PR_DATA" | python3 -c "
import json,sys
d = json.load(sys.stdin)
print('\n'.join(f['path'] for f in d['files']))
")

echo "PR: $PR — $PR_TITLE"
echo "Changed files:"
echo "$CHANGED_FILES"

bash

PR_DATA=$(gh pr view $PR --repo $REPO --json number,title,url,files,mergeCommit,baseRefName)
PR_TITLE=$(echo "$PR_DATA" | python3 -c "import json,sys; print(json.load(sys.stdin)['title'])")
PR_URL=$(echo "$PR_DATA" | python3 -c "import json,sys; print(json.load(sys.stdin)['url'])")
CHANGED_FILES=$(echo "$PR_DATA" | python3 -c "
import json,sys
d = json.load(sys.stdin)
print('\n'.join(f['path'] for f in d['files']))
")

echo "PR: $PR — $PR_TITLE"
echo "Changed files:"
echo "$CHANGED_FILES"

Step 2: Read Team Post-Deploy Configuration

步骤2：读取团队部署后配置

Read the team's CLAUDE.md for

post_deploy:

rules. Each rule maps a file glob pattern to an action:

yaml

undefined

读取团队的CLAUDE.md文件中的

post_deploy:

规则。每条规则将一个文件通配符模式映射到一个操作：

yaml

undefined

Example in team CLAUDE.md:

post_deploy:

match: "Dockerfile*" action: ecr-rebuild description: "Rebuild and push ECR image"
match: "docker-entrypoint.sh" action: ecr-rebuild
match: "crew.yml" action: config-reload-verify description: "Verify gateway reloaded updated config"
match: "scripts/*.sh" action: executor-verify description: "Spot-check executor behavior"
match: "event-rules.yml" action: config-reload-verify
match: "**" action: smoke-test optional: true description: "Optional smoke test for any PR"


**Action types:**

| Action | Description |
|--------|-------------|
| `ecr-rebuild` | Rebuild Docker image and push to ECR |
| `config-reload-verify` | Verify the process/gateway has reloaded the updated config |
| `executor-verify` | Spot-check executor or script behavior |
| `smoke-test` | Run team-defined smoke test |
| `custom` | Run `command` field as shell command |

post_deploy:

match: "Dockerfile*" action: ecr-rebuild description: "Rebuild and push ECR image"
match: "docker-entrypoint.sh" action: ecr-rebuild
match: "crew.yml" action: config-reload-verify description: "Verify gateway reloaded updated config"
match: "scripts/*.sh" action: executor-verify description: "Spot-check executor behavior"
match: "event-rules.yml" action: config-reload-verify
match: "**" action: smoke-test optional: true description: "Optional smoke test for any PR"


**操作类型：**

| 操作 | 描述 |
|--------|-------------|
| `ecr-rebuild` | 重建Docker镜像并推送到ECR |
| `config-reload-verify` | 验证进程/网关已重载更新后的配置 |
| `executor-verify` | 抽查执行器或脚本行为 |
| `smoke-test` | 运行团队定义的冒烟测试 |
| `custom` | 将`command`字段作为Shell命令运行 |

Step 3: Match Files to Actions

步骤3：匹配文件与操作

python

undefined

python

undefined

Pseudocode — implement in bash with Python for glob matching

import fnmatch

changed = CHANGED_FILES.splitlines() triggered_actions = []

for rule in post_deploy_rules: pattern = rule['match'] matching = [f for f in changed if fnmatch.fnmatch(f, pattern)] if matching: triggered_actions.append({ 'action': rule['action'], 'description': rule.get('description', rule['action']), 'matched_files': matching, 'optional': rule.get('optional', False) })

undefined

import fnmatch

changed = CHANGED_FILES.splitlines() triggered_actions = []

for rule in post_deploy_rules: pattern = rule['match'] matching = [f for f in changed if fnmatch.fnmatch(f, pattern)] if matching: triggered_actions.append({ 'action': rule['action'], 'description': rule.get('description', rule['action']), 'matched_files': matching, 'optional': rule.get('optional', False) })

undefined

Step 4: Execute Actions

步骤4：执行操作

Run each triggered action. Document result for each.

运行每个触发的操作，并记录每个操作的结果。

Action: ecr-rebuild

操作：ecr-rebuild

bash

undefined

bash

undefined

Rebuild and push ECR image

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}" ECR_URI="${ECR_URI:-$(grep 'fargate_ecr_uri' $PYLOT_DIR/crew.yml | awk '{print $2}')}"

cd "$PYLOT_DIR" bash scripts/build-worker-image.sh 2>&1 ECR_EXIT=$? [ $ECR_EXIT -eq 0 ] && echo "ecr-rebuild: success" || echo "ecr-rebuild: failed exit=$ECR_EXIT"

undefined

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}" ECR_URI="${ECR_URI:-$(grep 'fargate_ecr_uri' $PYLOT_DIR/crew.yml | awk '{print $2}')}"

cd "$PYLOT_DIR" bash scripts/build-worker-image.sh 2>&1 ECR_EXIT=$? [ $ECR_EXIT -eq 0 ] && echo "ecr-rebuild: success" || echo "ecr-rebuild: failed exit=$ECR_EXIT"

undefined

Action: config-reload-verify

操作：config-reload-verify

bash

undefined

bash

undefined

Verify the executor/gateway has reloaded the updated config

For Pylot: check that crew.yml timestamp matches what executor loaded

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}"

Check if executor is running and has loaded recent config

CREW_MTIME=$(stat -c %Y "$PYLOT_DIR/crew.yml" 2>/dev/null || stat -f %m "$PYLOT_DIR/crew.yml" 2>/dev/null) EXECUTOR_PID=$(pgrep -f "executor.sh" || true)

if [ -n "$EXECUTOR_PID" ]; then echo "config-reload-verify: executor running (pid=$EXECUTOR_PID). crew.yml mtime=$CREW_MTIME." echo "config-reload-verify: success — executor will pick up config on next poll cycle" else echo "config-reload-verify: WARNING — executor not running. Config will load on restart." fi

undefined

CREW_MTIME=$(stat -c %Y "$PYLOT_DIR/crew.yml" 2>/dev/null || stat -f %m "$PYLOT_DIR/crew.yml" 2>/dev/null) EXECUTOR_PID=$(pgrep -f "executor.sh" || true)

if [ -n "$EXECUTOR_PID" ]; then echo "config-reload-verify: executor running (pid=$EXECUTOR_PID). crew.yml mtime=$CREW_MTIME." echo "config-reload-verify: success — executor will pick up config on next poll cycle" else echo "config-reload-verify: WARNING — executor not running. Config will load on restart." fi

undefined

Action: executor-verify

操作：executor-verify

bash

undefined

bash

undefined

Spot-check executor behavior — run a quick test

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}"

Syntax-check the modified scripts

for script in $MATCHED_SCRIPTS; do bash -n "$PYLOT_DIR/$script" && echo "executor-verify: $script syntax OK" || echo "executor-verify: $script SYNTAX ERROR" done

undefined

for script in $MATCHED_SCRIPTS; do bash -n "$PYLOT_DIR/$script" && echo "executor-verify: $script syntax OK" || echo "executor-verify: $script SYNTAX ERROR" done

undefined

Action: smoke-test

操作：smoke-test

Run the team's configured smoke test. Optional by default.

bash

undefined

运行团队配置的冒烟测试。默认情况下为可选操作。

bash

undefined

Team-specific smoke test — read from CLAUDE.md smoke_test.command

Example for Pylot: run a dry-run event dispatch

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}" bash "$PYLOT_DIR/event-router.sh" --dry-run 2>&1 | head -20 echo "smoke-test: event-router dry-run complete"

undefined

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}" bash "$PYLOT_DIR/event-router.sh" --dry-run 2>&1 | head -20 echo "smoke-test: event-router dry-run complete"

undefined

Step 5: Post Summary Comment

步骤5：发布总结评论

bash

undefined

bash

undefined

Build table rows before heredoc (<<'EOF' prevents expansion — pre-build instead)

ACTION_TABLE="" for action_entry in $TRIGGERED_ACTION_ENTRIES; do ACTION_NAME=$(echo "$action_entry" | cut -d: -f1) ACTION_FILES=$(echo "$action_entry" | cut -d: -f2) ACTION_RESULT=$(echo "$action_entry" | cut -d: -f3) ACTION_TABLE="${ACTION_TABLE}| ${ACTION_NAME} | ${ACTION_FILES} | ${ACTION_RESULT} |\n" done [ -z "$ACTION_TABLE" ] && ACTION_TABLE="No file-match rules triggered for this PR's changed files.\n"

gh pr comment $PR --repo $REPO --body "$(printf '%s' "## Post-deploy actions

Action	Matched Files	Result
$(printf '%b' "$ACTION_TABLE")
Pipeline complete. This PR is live and verified.")"

undefined

ACTION_TABLE="" for action_entry in $TRIGGERED_ACTION_ENTRIES; do ACTION_NAME=$(echo "$action_entry" | cut -d: -f1) ACTION_FILES=$(echo "$action_entry" | cut -d: -f2) ACTION_RESULT=$(echo "$action_entry" | cut -d: -f3) ACTION_TABLE="${ACTION_TABLE}| ${ACTION_NAME} | ${ACTION_FILES} | ${ACTION_RESULT} |\n" done [ -z "$ACTION_TABLE" ] && ACTION_TABLE="No file-match rules triggered for this PR's changed files.\n"

gh pr comment $PR --repo $REPO --body "$(printf '%s' "## Post-deploy actions

Action	Matched Files	Result
$(printf '%b' "$ACTION_TABLE")
Pipeline complete. This PR is live and verified.")"

undefined

Step 6: Write Report

步骤6：生成报告

bash

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}"
REPORT="$PYLOT_DIR/reports/$(date +%Y-%m-%d)-post-deploy-$(echo $REPO | tr '/' '-')-pr${PR}.md"

cat > "$REPORT" <<EOF

bash

PYLOT_DIR="${PYLOT_DIR:-$HOME/projects/fellowship-dev/pylot}"
REPORT="$PYLOT_DIR/reports/$(date +%Y-%m-%d)-post-deploy-$(echo $REPO | tr '/' '-')-pr${PR}.md"

cat > "$REPORT" <<EOF

Post-Deploy: $REPO PR #$PR — $PR_TITLE

Date: $(date +%Y-%m-%d) PR: $REPO#$PR

Changed Files

$CHANGED_FILES

Actions Triggered

$TRIGGERED_ACTIONS_SUMMARY

Results

$ACTIONS_RESULTS EOF

---

$ACTIONS_RESULTS EOF

---

Default File-Match Rules (Pylot)

默认文件匹配规则（Pylot）

Pattern	Action	When
`Dockerfile*`	ecr-rebuild	Docker image changed
`docker-entrypoint.sh`	ecr-rebuild	Entrypoint script changed
`crew.yml`	config-reload-verify	Crew config changed
`event-rules.yml`	config-reload-verify	Event routing changed
`scripts/*.sh`	executor-verify	Shell scripts changed
`dispatch.sh`	executor-verify	Dispatch logic changed
`executor.sh`	executor-verify	Executor logic changed

模式	操作	触发场景
`Dockerfile*`	ecr-rebuild	Docker镜像变更
`docker-entrypoint.sh`	ecr-rebuild	入口脚本变更
`crew.yml`	config-reload-verify	Crew配置变更
`event-rules.yml`	config-reload-verify	事件路由变更
`scripts/*.sh`	executor-verify	Shell脚本变更
`dispatch.sh`	executor-verify	调度逻辑变更
`executor.sh`	executor-verify	执行器逻辑变更

Notes

注意事项

No matched rules = no actions. A PR touching only Markdown files does nothing. This is correct behavior.
Optional actions (smoke-test) run but do not affect the summary verdict.
ecr-rebuild failure should be surfaced as a comment but does not re-apply
```
deploy-failed
```
— the deploy itself was verified. File a follow-up issue instead.
Team config is the authority. Generic skill + team CLAUDE.md = full configurability without modifying the skill.
Monorepo: match files against per-target rules if the team has multiple deploy targets.

无匹配规则则不执行任何操作：仅修改Markdown文件的PR不会触发任何操作，这是正常行为。
可选操作（如冒烟测试）会运行，但不会影响总结结论。
ecr-rebuild失败应在评论中提示，但不会重新应用
```
deploy-failed
```
标签——因为部署本身已验证通过。应提交后续问题跟进。
团队配置为权威：通用技能 + 团队CLAUDE.md = 无需修改技能即可实现全配置化。
单体仓库：如果团队有多个部署目标，需针对每个目标的规则匹配文件。

post-deploy

Original

Translation

post-deploy

部署后操作

When to Use

使用场景

Invocation

调用方式

Runbook

运行手册

Step 0: Dedup Gate

步骤0：重复执行检查 gate

Check if post-deploy already ran (look for a post-deploy comment)

Check if post-deploy already ran (look for a post-deploy comment)

Step 1: Read PR Context

步骤1：读取PR上下文

Step 2: Read Team Post-Deploy Configuration

步骤2：读取团队部署后配置

Example in team CLAUDE.md:

Example in team CLAUDE.md:

Step 3: Match Files to Actions

步骤3：匹配文件与操作

Pseudocode — implement in bash with Python for glob matching

Pseudocode — implement in bash with Python for glob matching

Step 4: Execute Actions

步骤4：执行操作

Action: ecr-rebuild

操作：ecr-rebuild

Rebuild and push ECR image

Rebuild and push ECR image

Action: config-reload-verify

操作：config-reload-verify

Verify the executor/gateway has reloaded the updated config

Verify the executor/gateway has reloaded the updated config

For Pylot: check that crew.yml timestamp matches what executor loaded

For Pylot: check that crew.yml timestamp matches what executor loaded

Check if executor is running and has loaded recent config

Check if executor is running and has loaded recent config

Action: executor-verify

操作：executor-verify

Spot-check executor behavior — run a quick test

Spot-check executor behavior — run a quick test

Syntax-check the modified scripts

Syntax-check the modified scripts

Action: smoke-test

操作：smoke-test

Team-specific smoke test — read from CLAUDE.md smoke_test.command

Team-specific smoke test — read from CLAUDE.md smoke_test.command

Example for Pylot: run a dry-run event dispatch

Example for Pylot: run a dry-run event dispatch

Step 5: Post Summary Comment

步骤5：发布总结评论

Build table rows before heredoc (<<'EOF' prevents expansion — pre-build instead)

Build table rows before heredoc (<<'EOF' prevents expansion — pre-build instead)

Step 6: Write Report

步骤6：生成报告

Post-Deploy: $REPO PR #$PR — $PR_TITLE

Post-Deploy: $REPO PR #$PR — $PR_TITLE

Changed Files

Changed Files

Actions Triggered

Actions Triggered

Results

Results

Default File-Match Rules (Pylot)

默认文件匹配规则（Pylot）

Notes

注意事项