speckit-update

Original：🇨🇳 Chinese

Translated

Procedures for updating the base version of GitHub Spec Kit (https://github.com/github/spec-kit) and synchronizing templates/scripts. This is used when you need to update Spec Kit, apply differences from upstream releases, incorporate templates/commands/scripts, and maintain local operations (Japanese localization, no branch operations, SPEC-[8-digit UUID])

10installs

Sourceakiojin/skills

Added on2026-02-21

NPX Install

npx skill4agent add akiojin/skills speckit-update

SKILL.md Content (Chinese)

View Translation Comparison →

Spec Kit Update

GitHub Spec Kit: https://github.com/github/spec-kit

Overview

Reflect new releases of the official GitHub spec-kit into the

.specify/

directory of existing repositories, while maintaining existing operational rules (Japanese localization, no branch operations, SPEC ID format).

Workflow

1) Understand the Current Status

Identify the base version of spec-kit in the repository (example:
```
rg -n "v0\.0\.[0-9]+"
```
).
List targets derived from spec-kit (example:
```
.specify/
```
,
```
.claude/commands/speckit.*.md
```
).

2) Check Upstream Version

Check the latest tag/release of spec-kit on GitHub (via web search or tag list).
Determine the target tag for update, and retrieve it using
```
git clone
```
.

3) Obtain Differences

Get the diff between upstream tags, or the diff from upstream to local.
Focus on checking the changed targets:
- ```
templates/
```
- ```
templates/commands/
```
- ```
scripts/
```
  (bash/powershell)
- ```
memory/
```
Be sure to grasp any added/removed files.

4) Apply Locally

Reflect upstream changes to the local environment.
Reapply mandatory local constraints:
- All content must be in Japanese
- No branch creation/switching operations (ensure no checkout/switch/create remain in scripts/commands)
- SPEC ID must maintain the
```
SPEC-[8-digit UUID]
```
  format
If there are existing operational differences, record a brief reason.

5) Update Documentation

Update version notations (example:
```
CLAUDE.md
```
,
```
.specify/README.md
```
).
Add entries to the update history if available.

6) Verification and Reporting

Briefly verify the operation of key scripts (e.g.,
```
--help
```
,
```
--json
```
).
Use
```
rg
```
to check for remaining English content or old version notations.
Clearly report the summary of changes, scope of impact, and unaddressed differences.

Guardrails

Do not create/switch branches (managed by users).
Always maintain the
```
SPEC-[8-digit UUID]
```
format for SPEC IDs.
Translate upstream English templates into Japanese before reflecting them.