SuperAPI AI Directory

tier-judge

General & other

View repository

Updated 10-15 20:04

About this skill

tier-judge — git diff → Tier 1/2/3 automatic judgment

git diff main...HEAD and suggest the PR Tier. Output the basis for the judgment and boundary case warnings to support the human's final confirmation.


Usage

「このブランチのTierを判定して」
「git diffを見てTierを教えて」
「PR作る前にTier確認したい」

Judgment flow

Step 1: Tier 3 check (if even one applies → Tier 3)

Check whether the changes include any of the following:

Check item Detection pattern example
Price/cost rate price, pricing, ¥, $29, cost, rate(in code)
Authentication/security .envEdit, oauth, api_key, token, secret(in code)
DB schema destructive change DROP TABLE, RENAME, ALTER COLUMN TYPE, NOT NULLAdd + backfill
Production environment configuration vercel.json, wrangler.toml, secrets:, GitHub Actions secrets
hook/settings affects all departments validate-dangerous-ops-v2.sh, settings.local.json(distribution target)
Changes from the template department claude-code-template/ Code changes under (affects all departments)
Introduction of a new external service New API key configuration, new npm install Addition of external dependency via package

Step 2: Tier 1 check (no code → Tier 1)

When the changed files are only the following:

  • *.md, *.txt, *.csv
  • Only test file additions (no changes to existing code)
  • Only copies, documents, and data files

Step 3: Tier 2 (code changes other than the above)

Code changes present + does not meet Tier 3 conditions → Tier 2

Tier 2 exception(even if some Tier 3 conditions apply, Tier 2):

  • CREATE TABLE, ADD COLUMN nullable, index addition only → pure additive DB schema
  • When changes to hook/settings affect only within the same peer

Output format

## Tier判定結果: Tier [1/2/3]

**根拠:**
- [判定の主な理由を箇条書き]

**Tier 2の場合 — レビュー担当:**
| 自分 | レビュー依頼先 |
|------|-------------|
| template課 | reserch課 |
| mued課 | native課 |
| native課 | mued課 |
| SNS課 | write課 |
| write課 | SNS課 |
| video課 | SNS課 |
| LP課 | mued課 |
| data課 | mued課 |
| freee課 | LP課 |

**境界ケース注意(該当する場合のみ):**
- [境界ケースの警告と推奨対応]

Boundary case examples

price When the string is included in the slug:

⚠ `pricing-page.tsx` の変更を検知しましたが、コード内容はUI文言変更のみです。
価格・原価率への影響はないと判断しますが、確認してください。→ Tier 2のまま

Unintended changes to secret-related files:

⚠ `.env.example` に `SECRET_KEY` の追記を検知しました。
.env.example は許容範囲ですが、意図的な変更か確認してください。→ Tier 2のまま
(実際の秘密鍵が混入している場合は Tier 3に上げてください)

Changes to settings.local.json:

⚠ `.claude/settings.local.json` の変更を検知しました。
全課配布対象か、自ピア内のみの変更かを確認してください。
- 全課配布対象 → Tier 3
- 自ピア内のみ → Tier 2

Notes

  • Keyword matching can produce false positives. Always check the basis for the judgment
  • The final decision is made by a human. The principle is "when in doubt, raise to Tier 3"
  • If the git diff is large (over 100 files), analyze only the main files and clearly state that