Verify Composite Expansion

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.

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

Example:

.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:

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:

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:

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

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

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:

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

Converted and distributed by TomeVault — claim your Tome and manage your conversions.