メニュー
AI repo versioning and changelogs via release-please — never edit CHANGELOG.md or pyproject version by hand. Use when the user asks about releases, version bumps, changelogs, or preparing a release.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
ALWAYS use this skill whenever you would otherwise ask the user a question in free-form chat -- for clarifications, confirmations (especially destructive actions), missing parameters, multiple-choice decisions, or structured form input. Elicitations are routed through the Unique AI Platform UI via `unique-cli elicit create` + `elicit wait` (or `elicit ask` outside an agent harness) so the user gets a proper structured prompt and you get a structured answer back. Do NOT ask the user in plain chat when you can use this skill instead.
Read Agentic Table (magic table / due-diligence) sheets through the unique-cli agentic-table command. Use when the user or task involves inspecting an Agentic Table: a sheet's state and metadata, a specific cell's value or lock state, a cell's edit/answer history, or the sheet's generated export artifacts (reports, question exports). These are read-only (Tier 0) commands — they never modify the sheet and never require confirmation. Access to each sheet is enforced by the platform; a denial is reported as `agentic-table: permission denied`.
Call MCP (Model Context Protocol) server tools on the Unique AI Platform using the unique-cli mcp command. Use when the user asks to invoke, call, or execute an MCP tool, or when they need to send a JSON payload to an MCP server through the CLI. The JSON payload is forwarded 1:1 to the platform's MCP call-tool API.
Invoke connected Unique spaces/subagents through the unique-cli subagent command. Use when the workspace exposes connected-space tools and you need to delegate a question or task to one of those configured assistants.
Search the Unique AI Platform knowledge base using the unique-cli search command, with automatic per-turn citation tracking so cited facts render as clickable reference chips and `<sup>N</sup>` footnotes on the Unique platform. Use whenever the user asks to find, search, or query documents or content on Unique, including filtering by folder or metadata. Also covers `unique-cli read <cont_id>` for reading the full indexed text of a document when its content ID is already known. NOTE: This search uses combined vector + full-text indexing. Excel (.xlsx/.xls), CSV (.csv), and image files are NOT full-text indexed, so they will not appear in search results. To locate these file types, use the unique-cli-file-management skill instead (browse folders with `unique-cli ls` to find them by name).
Search the documents uploaded for the CURRENT task/row (e.g. an Agentic Table row's attached files) via the `unique-cli uploaded-search "<query>"` command, with the same per-turn citation tracking as `unique-cli search` so cited facts render as `<sup>N</sup>` footnotes and clickable reference chips on the Unique platform. ALWAYS use this skill when the user refers to documents they uploaded/attached to this task, or when you need facts from the task's own attached files. These uploaded files are scoped to the chat, NOT to a knowledge-base folder, so they will NEVER appear in `unique-cli search` results no matter the folder or metadata filters. Use `unique-cli search` for the knowledge base and this command for the task's uploaded documents; the two are complementary and citation numbering is shared across them within a turn.
| name | release-process |
| description | AI repo versioning and changelogs via release-please — never edit CHANGELOG.md or pyproject version by hand. Use when the user asks about releases, version bumps, changelogs, or preparing a release. |
| license | MIT |
| compatibility | claude cursor opencode |
| metadata | {"version":"1.0.0","languages":"all","audience":"developers","workflow":"documentation","since":"2026-05-22"} |
Versions and changelogs in this repo are fully automated. Do not manually edit release artifacts in feature PRs.
CHANGELOG.mdversion = "..." in each package pyproject.toml.release-please-manifest.jsonConfig: release-please-config.json and manifest at repo root. Full lifecycle: docs/contributing/release-process.md.
.github/scripts/check-no-manual-release.sh fails PRs that modify:
CHANGELOG.md.release-please-manifest.jsonversion = "..." line in any pyproject.tomlException: release-please's own standing Release PR (opened by the Release Workflow App).
git-conventional-commits skill).feat(sdk): ..., feat(toolkit): ...).chore: stable release main per group-pull-request-title-pattern in release-please-config.json; target CalVer is in the PR diff, not the title).| Intent | Commit type | Notes |
|---|---|---|
| New feature | feat(scope): ... | Appears under release notes |
| Bug fix | fix(scope): ... | Bug Fixes section |
| Breaking change | feat(scope)!: ... + BREAKING CHANGE: footer | Major bump per package |
| Internal deps only | chore(deps): ... | Hidden from user-facing changelog |
CalVer scheme: YYYY.WW.PATCH — see docs/contributing/release-process.md.
Do not edit CHANGELOG.md or pyproject.toml version. Instead:
docs/contributing/release-process.md for hotfixes/RC/dev cuts.release/*Backport fixes from main with cherry-pick, not direct edits on the release branch.
| Rule | Why |
|---|---|
Cherry-pick from main | CI checks patch equivalence (git cherry vs main), not identical SHAs |
| Rebase and merge only | Squash collapses N commits → 1; release-please loses per-commit changelog entries |
| Conventional commit subjects | release-please attributes each merged commit to changelog sections |
| Skip release-please bot PRs | chore: hotfix release/... PRs are automation — CI skips lineage for release-please--* branches |
Script: .github/scripts/check-release-lineage.sh (runs in CI for human PRs targeting release/*; patch-equivalence only, no commit-metadata allowlist).
Bumping a published unique_toolkit / unique_sdk version inside the monorepo (e.g. assistants-core pyproject.toml) is a separate step after a stable AI release — not a manual ai-repo changelog edit. See model-deployment LESSONS-LEARNED for cherry-pick checklists.
hotfix-backport — cherry-pick workflow and rebase-merge rules for release/*git-conventional-commits — commit/PR title formatsecurity-maintenance — same no-manual-release rules for CVE/CodeQL PRs