deploy

Category: Development & Coding | Uploader: wlfghdr | Downloads: 0 | Version: v1.0（Latest）

Release template or framework file changes — branch off main if needed, commit, open a PR, verify all GitHub Actions CI checks are green, merge, and return to main

Changelog: Source: GitHub https://github.com/wlfghdr/agentic-enterprise

Directory Structure

Current level: .claude/skills/deploy/

📄 SKILL.md 4.1 KB

SKILL.md

---
name: deploy
description: Release template or framework file changes — branch off main if needed, commit, open a PR, verify all GitHub Actions CI checks are green, merge, and return to main
argument-hint: "[optional: description of what changed]"
disable-model-invocation: true
allowed-tools: Bash(git *), Bash(gh *)
---

You are executing the template release workflow for the agentic-enterprise repository.

$ARGUMENTS

## Step 0 — Scope check

Confirm the changed files are **template or framework files** (not instances):

- `_TEMPLATE-*.md` files anywhere in `org/`
- `AGENT.md` files at each layer (`org/*/AGENT.md`)
- `AGENTS.md` / `CLAUDE.md`
- Quality policies in `org/4-quality/policies/`
- `CONFIG.yaml`, `OPERATING-MODEL.md`, integration definitions in `org/integrations/`


---

## Step 1 — Verify version and date fields

Run `git diff --stat` to list all changed files.

For each changed file, confirm its version/date fields are updated per Rule 10 in `AGENTS.md`:

| File type | What to update |
|---|---|
| `AGENT.md` files | `Version` (minor or major bump) + `Last updated` date |
| `_TEMPLATE-*.md` files | `Template version` + `Last updated` date + new row in `## Changelog` |
| Quality policies | `Version` + `Last updated` date |
| `CONFIG.yaml` | `framework_version` |
| `AGENTS.md` / `CLAUDE.md` | `Last updated` date (if field present) |

Fix any missing fields before proceeding.

---

## Step 2 — Add changelog entry

For each changed file:
- If the file has a `## Changelog` section → add a row: `| <date> | <version> | <what changed and why> |`
- If not → add an entry to root `CHANGELOG.md` under the correct version section

The entry must explain **what** changed and **why** — not just "updated file".

---

## Step 3 — Ensure you are on a feature branch

Check the current branch:

```bash
git branch --show-current
```

**If you are on `main`:** create a descriptive feature branch now — do this before committing:

```bash
git checkout -b <type>/<short-description>
```

Use the same `<type>` prefix you will use for the commit message (`feat`, `fix`, `docs`, `refactor`). Example: `docs/update-agent-versioning-rules`.

**If you are already on a feature branch:** continue to Step 4.

> Direct pushes to `main` are blocked by branch protection. All changes must go through a Pull Request.

---

## Step 4 — Commit

Stage only the files you intentionally changed — do not use `git add -A` or `git add .` blindly.

Commit message format:
```
<type>: <short summary (≤72 chars)>

<body: what problem does this solve / what decision was made>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
```

Allowed types: `feat` (new content), `fix` (correction), `docs` (prose only), `refactor` (restructure without meaning change).

Confirm the commit was created successfully.

---

## Step 5 — Push and open Pull Request

Push the branch:

```bash
git push -u origin <branch>
```

Then open a Pull Request:

```bash
gh pr create --title "<type>: <short summary>" --body "$(cat <<'EOF'
## Summary
<what changed and why>

## Files changed
<list the key files>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
```

Confirm the PR URL and note the PR number.

---

## Step 6 — Watch CI

```bash
gh run list --limit 3
```

Wait for all checks on the PR branch to complete, then inspect:

```bash
gh run view <run-id>
```

**All checks green → proceed to Step 7.**

**Any check red:**
1. Read the failure log: `gh run view <run-id> --log-failed`
2. Diagnose the root cause — read the actual output, do not guess
3. Fix the issue; if the fix touches governed files, update their version/date fields
4. Return to Step 4 and repeat
5. Do **not** proceed to Step 7 while any check is red

---

## Step 7 — Merge PR and return to main

Once all CI checks are green, merge the PR:

```bash
gh pr merge <pr-number> --squash --delete-branch
```

Then switch the local working copy back to `main` and pull the merged commit:

```bash
git checkout main && git pull
```

Confirm the local `main` is up to date with the merged changes and report success with the PR URL.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

deploy

Directory Structure

SKILL.md

Report

Notice