メニュー
Use when you need to check the current plugin version, latest published release, and what changed between them.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | team-shinchan:version |
| description | Use when you need to check the current plugin version, latest published release, and what changed between them. |
| user-invocable | true |
node -e "const p=JSON.parse(require('fs').readFileSync('${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json','utf-8'));console.log(p.version)"
Store result as CURRENT_VERSION.
gh release list --repo seokan-jeong/team-shinchan --limit 1 --json tagName,publishedAt --jq '.[0]' 2>/dev/null || echo '{"error":"gh not available or no releases"}'
Extract tag name and strip leading v to get PUBLISHED_VERSION.
Extract publishedAt as PUBLISHED_DATE.
If gh fails or no releases found, set PUBLISHED_VERSION = "unknown".
Compare CURRENT_VERSION vs PUBLISHED_VERSION:
CURRENT_VERSION > PUBLISHED_VERSION: local is ahead (unreleased changes exist)CURRENT_VERSION == PUBLISHED_VERSION: local is up to dateCURRENT_VERSION < PUBLISHED_VERSION: local is behind (update available)If versions differ, read CHANGELOG.md and extract all entries between the two versions.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Team-Shinchan Version Info
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Local version: v{CURRENT_VERSION}
Published version: v{PUBLISHED_VERSION} ({PUBLISHED_DATE})
Status: {ahead|up to date|behind}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If versions differ, also show:
Changes between v{LOWER} and v{HIGHER}:
{changelog entries — keep concise, show Added/Changed/Fixed sections}
If local is behind, suggest:
To update: claude plugin update team-shinchan
If local is ahead, suggest:
Unreleased changes detected. Use /team-shinchan:release --version <X.Y.Z> to publish.
Use when you have a large-scale, multi-phase project requiring orchestrated execution.
Use when you need persistent looping until a task is fully complete.
Deterministic adversarial code review for high-stakes scope — independent per-dimension review, a non-skippable per-finding refutation, completeness + interaction critics, and a deterministic 3-lens rubric judge panel. Opt-in main-loop Workflow tier.
Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
Deterministic competitive code tournament — N builders independently solve one task and return patches, an Action-Kamen judge scores them head-to-head, the winner is picked by score and applied. Opt-in main-loop Workflow tier.
Deterministic adversarial debate for high-stakes or irreversible decisions — mandatory refutation plus a scored judge panel. Opt-in main-loop Workflow tier.