ワンクリックでManusで任意のスキルを実行

release

スター8

フォーク1

更新日2026年6月23日 21:27

Prepare an IntexuraOS release by collecting release data, triaging changes, updating docs, versions, changelog, website release highlights, and GitHub release notes.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

pbuchman

pbuchman/intexuraos

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Release Skill

Use this skill to prepare an IntexuraOS release.

Usage

$release                    # Full release workflow
$release --skip-docs        # Skip service documentation
$release --phase 3          # Resume from a specific phase
$release --collect          # Only collect and triage release data

Codex Execution Model

Use subagent-driven execution first whenever Codex subagent tools are available.
Before Phase 1, create a short release execution plan and use the superpowers:subagent-driven-development pattern: bounded subagent tasks, controller integration, spec/quality review loops for mutating work, and final controller verification.
Fall back to current-session execution only when subagent tools are unavailable; report that fallback before continuing.
Do not create git worktrees for this repo. .claude/CLAUDE.md forbids worktrees, so all release work stays in the active checkout while subagents use their normal forked workspaces.
Former release-agent instructions live in reference/agent-prompts.md; use them as subagent task prompts by default.
Use the existing $share skill or the explicit GCS upload commands in the workflow when publishing the prioritizer page.
Follow project rules from .claude/CLAUDE.md for branch, commit, CI, and PR behavior.

Invocation Detection

Argument	Workflow	What Happens
none	`workflows/full-release.md`	Full release workflow
`--skip-docs`	`workflows/full-release.md`	Full release workflow, skipping service documentation
`--phase N`	`workflows/full-release.md`	Resume from Phase N
`--collect`	`workflows/collect-release-data.md`	Separate pipeline: collect release data, triage it, write `.prerelease-data.md`, then stop

--collect is not a modifier of the full release workflow. It runs the collection pipeline and exits. The full workflow can later consume .prerelease-data.md when it is fresh for the current HEAD.

Core Mandates

Feature prioritization happens once in Phase 1 using the interactive prioritizer page.
Notable changes and minor fixes bypass the prioritizer and are automatically included in the changelog unless netted out.
Service documentation runs silently through bounded subagent tasks by default.
pnpm run ci:tracked must pass before any release commit.
All package versions must stay synchronized across root, apps, packages, and workers.
Finalization must use a feature branch and a PR targeting development; do not commit directly to development or main.
Tags must point to a commit contained in origin/main.
GitHub Release notes must mirror the sorted CHANGELOG categories.
Post-release validation must verify tag, release, changelog, package versions, and branch state.

Phase Overview

Phase	Name	Interaction	Key Actions
0	Subagent Plan	Automatic	Build the subagent-driven execution plan and choose fallback only if tools are unavailable
1	Kickoff	User Input	Analyze semver, create prioritizer page, parse user priorities
2	Service Docs	Silent	Update service docs through bounded workers and validate factual accuracy
3	High-Level Docs	Automatic	Update `docs/overview.md`, README badges, and `docs/services/index.md`
4	README	Automatic	Generate or update README "What's New" from highlighted release features
5	Website	Automatic	Update homepage version strings and `WhatsNewSection`
6	Finalize	Automatic	Sync versions, update changelog, run CI, commit on feature branch, open PR, tag main after merge

Tool Verification

Before release operations, verify required tools:

Tool	Verification Command	Purpose
Git	`git --version`	Version control
GitHub CLI	`gh auth status`	PR and release actions
Node.js	`node --version`	Package scripts
gsutil	`gsutil version`	Prioritizer page upload
jq	`jq --version`	JSON transforms

If any required tool is unavailable, stop and report the failing tool, purpose, and fix.

References

Full workflow: workflows/full-release.md
Collection workflow: workflows/collect-release-data.md
Website audit workflow: workflows/website-audit.md
Former agent prompts: reference/agent-prompts.md
Subagent execution: reference/subagent-execution.md
Semver analysis: reference/semver-analysis.md
Phase checklist: reference/phase-checklist.md
Templates: templates/

このリポジトリの他の Skills

同じリポジトリ

document-service

pbuchman/intexuraos

Generate professional documentation for IntexuraOS services (apps, workers, packages). Produces 5 doc files per service, 3 per package, plus aggregated site content and cross-validation reports. Supports interactive, autonomous, and team-of-agents modes. Use when documenting services, generating docs, updating documentation, or validating doc consistency.

2026-06-238

release

pbuchman/intexuraos

Orchestrate a 6-phase release workflow with automated service documentation, high-level docs updates, README "What's New" section, website improvements, and semantic versioning. Use when preparing a new release.

2026-06-238

sentry

pbuchman/intexuraos

Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry.

2026-06-238

commit-push

pbuchman/intexuraos

Use when the user says "commit push", "commit and push", "push a PR", or asks Codex to finalize IntexuraOS changes by committing, pushing, and opening a pull request against development.

2026-06-128

debug-code-task

pbuchman/intexuraos

Use when user pastes a dev.intexuraos.cloud or intexuraos.cloud code-task URL and asks to debug, investigate, or understand what went wrong. Also use when user mentions a code task ID (task_*) with investigation intent.

2026-04-238

nitpick-nuker

pbuchman/intexuraos

Autonomous PR comment triage - fixes review feedback until CI passes

2026-04-108

Release Skill

Use this skill to prepare an IntexuraOS release.

Usage

$release # Full release workflow $release --skip-docs # Skip service documentation $release --phase 3 # Resume from a specific phase $release --collect # Only collect and triage release data

Codex Execution Model

Use subagent-driven execution first whenever Codex subagent tools are available.

Before Phase 1, create a short release execution plan and use the superpowers:subagent-driven-development pattern: bounded subagent tasks, controller integration, spec/quality review loops for mutating work, and final controller verification.

Fall back to current-session execution only when subagent tools are unavailable; report that fallback before continuing.

Do not create git worktrees for this repo. .claude/CLAUDE.md forbids worktrees, so all release work stays in the active checkout while subagents use their normal forked workspaces.

Former release-agent instructions live in reference/agent-prompts.md; use them as subagent task prompts by default.

Use the existing $share skill or the explicit GCS upload commands in the workflow when publishing the prioritizer page.

Follow project rules from .claude/CLAUDE.md for branch, commit, CI, and PR behavior.

Invocation Detection

Argument

Workflow

What Happens

none

workflows/full-release.md

Full release workflow

--skip-docs

workflows/full-release.md

Full release workflow, skipping service documentation

--phase N

workflows/full-release.md

Resume from Phase N

--collect

workflows/collect-release-data.md

Separate pipeline: collect release data, triage it, write .prerelease-data.md, then stop

--collect is not a modifier of the full release workflow. It runs the collection pipeline and exits. The full workflow can later consume .prerelease-data.md when it is fresh for the current HEAD.

Core Mandates

Feature prioritization happens once in Phase 1 using the interactive prioritizer page.

Notable changes and minor fixes bypass the prioritizer and are automatically included in the changelog unless netted out.

Service documentation runs silently through bounded subagent tasks by default.

pnpm run ci:tracked must pass before any release commit.

All package versions must stay synchronized across root, apps, packages, and workers.

Finalization must use a feature branch and a PR targeting development; do not commit directly to development or main.

Tags must point to a commit contained in origin/main.

GitHub Release notes must mirror the sorted CHANGELOG categories.

Post-release validation must verify tag, release, changelog, package versions, and branch state.

Phase Overview

Phase

Name

Interaction

Key Actions

Subagent Plan

Automatic

Build the subagent-driven execution plan and choose fallback only if tools are unavailable

Kickoff

User Input

Analyze semver, create prioritizer page, parse user priorities

Service Docs

Silent

Update service docs through bounded workers and validate factual accuracy

High-Level Docs

Automatic

Update docs/overview.md, README badges, and docs/services/index.md

README

Automatic

Generate or update README "What's New" from highlighted release features

Website

Automatic

Update homepage version strings and WhatsNewSection

Finalize

Automatic

Sync versions, update changelog, run CI, commit on feature branch, open PR, tag main after merge

Tool Verification

Before release operations, verify required tools:

Tool

Verification Command

Purpose

Git

git --version

Version control

GitHub CLI

gh auth status

PR and release actions

Node.js

node --version

Package scripts

gsutil

gsutil version

Prioritizer page upload

jq --version

JSON transforms

If any required tool is unavailable, stop and report the failing tool, purpose, and fix.

References

Full workflow: workflows/full-release.md

Collection workflow: workflows/collect-release-data.md

Website audit workflow: workflows/website-audit.md

Former agent prompts: reference/agent-prompts.md

Subagent execution: reference/subagent-execution.md

Semver analysis: reference/semver-analysis.md

Phase checklist: reference/phase-checklist.md

Templates: templates/

name	release
description	Prepare an IntexuraOS release by collecting release data, triaging changes, updating docs, versions, changelog, website release highlights, and GitHub release notes.