# Verify Composite Expansion

> 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". Use when this capability is needed.

- Skill: `tomevault-io/verify-composite-expansion` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/verify-composite-expansion`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/verify-composite-expansion/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/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.

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

Example:

```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

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/kesin11) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->