メニュー
Release a new YAMLGraph version. Use when: bumping version, creating a release, tagging, pushing a release, freezing changelog, or handling pre-commit hook cascades during release.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Author YAMLGraph prompt YAML files. Use when: writing prompt templates, configuring inline schemas or output_schema, using Jinja2 templates, adding system/user messages, defining structured output fields, or using system_segments for prompt caching.
Author YAMLGraph graph YAML files. Use when: creating or editing graph YAML, adding nodes or edges, configuring routing and conditions, setting up state keys, variables, data_files, tools, loop limits, error handling, or verification gates.
Operate the Chaplain automation system. Use when: starting the chaplain, checking pipeline status, submitting proposals to inbox, debugging pipeline failures, retrying failed topics, cleaning worktrees, running the philosopher or inquisitor.
Create and manage YAMLGraph feature requests. Use when: writing a feature request, planning a feature, following the plan-judge-enforce workflow, submitting a proposal to the chaplain inbox, understanding the FR lifecycle, or writing acceptance criteria.
Run code quality analysis on YAMLGraph. Use when: running ruff, bandit, radon, vulture, pytest coverage, checking code quality, finding dead code, security scanning, or generating improvement recommendations. For autonomous analysis, use the code-analysis agent instead.
Check LangSmith traces for YAMLGraph runs. Use when: debugging graph execution, reviewing LLM latency or token usage, investigating failed runs, verifying tracing config, querying recent traces, troubleshooting LangSmith connectivity.
| name | release-version |
| description | Release a new YAMLGraph version. Use when: bumping version, creating a release, tagging, pushing a release, freezing changelog, or handling pre-commit hook cascades during release. |
| argument-hint | version number like '0.4.62' |
Bump, commit, push, and tag a YAMLGraph release. Canonical source: reference/release-checklist.md.
scripts/release.sh 0.4.XX
git push && git push --tags
The script handles: validate changelog fragments → freeze to changelog/0.4.XX/ → bump pyproject.toml → regenerate CHANGELOG.md → commit → tag.
git pull
cat > changelog/unreleased/FR-XXX-feature-name.md << 'EOF'
---
type: feat
scope: component
req: REQ-YG-XXX
---
- **FR-XXX Feature Name**: Description. (REQ-YG-XXX)
EOF
Fragment type: values: feat → Added, fix → Fixed, removal → Removed.
sed -i '' 's/version = "X.Y.Z"/version = "X.Y.W"/' pyproject.toml
VERSION="X.Y.W"
mkdir -p "changelog/${VERSION}"
mv changelog/unreleased/*.md "changelog/${VERSION}/"
python scripts/aggregate_changelog.py > CHANGELOG.md
cat > tmp/msg.txt << 'EOF'
chore(release): vX.Y.W
EOF
git add -A
git commit -F tmp/msg.txt
Hooks will likely auto-fix files on first attempt. Re-stage and retry:
git add -A && git commit -F tmp/msg.txt
git push
git tag vX.Y.W
git push --tags
gh run list --limit 5 --json name,status,conclusion,headBranch \
--jq '.[] | "\(.status) \(.conclusion // "—") \(.name) \(.headBranch)"'
gh release create vX.Y.W --title "vX.Y.W" --generate-notes
| Hook | Fix |
|---|---|
ruff | Auto-fixes style; re-stage |
ruff-format | Auto-fixes format; re-stage |
trailing-whitespace | Auto-fixes; re-stage |
req_coverage | Add capability YAML to capabilities/ |
When req_coverage --strict fails:
cat > capabilities/CAP-XX-feature-name.yaml << 'EOF'
id: CAP-XX
name: Feature Name
fr: FR-XXX
requirements:
- id: REQ-YG-XXX
description: Brief description
EOF
Always write to file to avoid dquote trap:
cat > tmp/msg.txt << 'EOF'
feat(scope): FR-XXX summary
- Detail 1
- Detail 2
EOF
git commit -F tmp/msg.txt