メニュー
ChangeLog.md format spec for VibeCodeHPC. Use when writing or validating ChangeLog entries with compile/job/test/sota fields.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Compute budget management with phase-based termination criteria. Use when checking budget, determining project phase, or making stop decisions.
Compiler warning triage for HPC parallelization. Use when deciding whether to proceed with job execution after compile warnings.
Context window usage monitoring and auto-compact recovery. Use when context is filling up or after auto-compact occurs. Optional for strong models.
CLI and dependency installation guidance. Use when setting up VibeCodeHPC on a new environment — local PC, supercomputer, container, etc.
Hardware spec collection and theoretical peak performance calculation for HPC environments. Prerequisite: skills/ssh-management for remote access.
Evolutionary flat-directory exploration strategy for HPC optimization. Use when designing directory hierarchies or planning multi-generation parallelization strategies.
| name | changelog-format |
| description | ChangeLog.md format spec for VibeCodeHPC. Use when writing or validating ChangeLog entries with compile/job/test/sota fields. |
### vX.Y.Z
**Changes**: "brief description"
**Result**: key metric `value`
**Comment**: "implementation notes"
<details>
- **generated_at**: `YYYY-MM-DDTHH:MM:SSZ` (UTC)
- [x/✗] **compile**
- status: `success|warning|error`
- message: "error/warning text" (if applicable)
- log: `path/to/log`
- [x/✗] **job**
- id: `job_id`
- resource_group: `group_name` # required for budget
- start_time / end_time: `ISO8601` # required for budget
- runtime_sec: `seconds`
- status: `success|error|timeout|cancelled|running`
- [x/✗] **test**
- performance: `value`
- unit: `GFLOPS|seconds|...`
- accuracy: `value` (if applicable)
- [x/✗] **sota**
- scope: `local|family|hardware|project` (on update only)
- **params**: nodes, block_size, etc.
</details>
<details> folding is mandatoryresource_group, start_time, end_time, runtime_sec required for budget tracking (regex-parsed)<details> via project-specific templatepython3 ${CLAUDE_SKILL_DIR}/scripts/changelog.py --help
python3 ${CLAUDE_SKILL_DIR}/scripts/changelog.py create --version 1.2.0 --changes "Optimized loop tiling"
python3 ${CLAUDE_SKILL_DIR}/scripts/changelog.py append /path/to/ChangeLog.md --version 1.2.0 --changes "Added vectorization"
python3 ${CLAUDE_SKILL_DIR}/scripts/changelog.py validate /path/to/ChangeLog.md
references/changelog_api.md — Python analytics API for SE statistical analysisreferences/pm_override_template.md — Example template for PM to customize ChangeLog fields within <details> (project-specific params, metrics, SOTA extensions)