AgentSkillsCN

verify-composite-expansion

通过对比 CLI 生成的 Mermaid 图表与实际的 GitHub Actions 日志，验证复合操作展开的输出。当您针对任意 GitHub Actions 工作流运行测试或调试 --expand-composite-actions 功能时，可使用此方法。触发关键词包括：“验证复合操作展开”、“核实复合操作展开”或“将 CLI 输出与日志进行比对”。

SKILL.md
--- frontmatter
name: verify-composite-expansion
description: Verify composite action expansion output by comparing CLI-generated mermaid charts with actual GitHub Actions logs. Use when testing or debugging the --expand-composite-actions feature against any GitHub Actions workflow run. Triggered by requests like "composite展開を検証", "verify composite expansion", or "compare CLI output with logs".

Verify Composite Expansion

Verify the correctness of composite action expansion by comparing CLI output with actual GitHub Actions logs.

Workflow

1. Run the verification script

Use scripts/verify_composite.sh to collect all data at once.

bash
bash .claude/skills/verify-composite-expansion/scripts/verify_composite.sh <org/repo> <run_id> [output_dir]

Example:

bash
bash .claude/skills/verify-composite-expansion/scripts/verify_composite.sh directus/directus 21767232907 .

The script performs:

  1. •Run CLI with --expand-composite-actions=true → {repo}_composite.md
  2. •Run CLI without the flag → {repo}.md
  3. •gh run view to list jobs
  4. •Fetch step details for each job via GitHub API
  5. •Show first 50 lines of logs for each job

2. Running individual commands manually

With composite expansion:

bash
deno run --allow-net --allow-env --allow-write cli.ts --token "$(gh auth token)" --expand-composite-actions=true "https://github.com/{org}/{repo}/actions/runs/{run_id}" -o {repo}_composite.md

Without composite expansion:

bash
deno run --allow-net --allow-env --allow-write cli.ts --token "$(gh auth token)" "https://github.com/{org}/{repo}/actions/runs/{run_id}" -o {repo}.md

List jobs:

bash
gh run -R {org}/{repo} view {run_id}

Get step details for a job (gaps in step numbers indicate composite sub-steps):

bash
gh api repos/{org}/{repo}/actions/jobs/{job_id} --jq '.steps[] | "\(.number)\t\(.name)\t\(.started_at)\t\(.completed_at)"'

View actual logs for a job:

bash
gh run -R {org}/{repo} view --job={job_id} --log

3. Verification checklist

When comparing outputs, check:

  • •Without expansion: Composite actions appear as a single step (e.g., "Prepare (25s)")
  • •With expansion: That step is expanded into sub-steps with (sub) prefix
  • •API step numbers: Gaps in numbering correspond to composite sub-steps
  • •Time consistency: Total duration of sub-steps roughly matches the single composite step duration