agentleFS
shimo4228shimo4228/zenn-content/.claude/skills/quality-gate/SKILL.md

quality-gate

Skill3 starsChanged 14 days agoCC0-1.0View on GitHub

人間向け公開物の受け入れゲート。完成稿と project の publication channel contract を読み、必須 reviewer verdict・機械検査・著者のタイトル選択が揃ったかを集約して PASS / FAIL / BLOCKED を返す。Use when — 公開直前、他人の原稿を公開してよいか確認するとき、/quality-gate <file>。NOT for — prose の再レビュー(→ editor / essay-reviewer / prose-clarity-reviewer)、タイトル候補の生成と点検(→ headline-craft)、公開操作(→ project-local publishing skill)、paper / README の専用ゲート。

45 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use deploy.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

The file

Files
SKILL.md

quality-gate — publication acceptance aggregator

公開可否を新しく評価せず、project が宣言した受け入れ条件の完了を照合する。媒体名、reviewer 名、frontmatter、CLI、公開手順は本 skill にハードコードしない。

Input

  • 完成稿の path
  • <project>/.claude/rules/*.md の publication channel contract
  • contract が要求する reviewer report / deterministic check result
  • 本文の最後の構造変更より後の、著者のタイトル選択

contract は対象 path ごとに少なくとも次を宣言する:

  • channel / path matcher
  • required reviewers と blocking verdict
  • required deterministic checks
  • title constraints
  • publish handoff

Procedure

  1. 原稿 path を local contract の 1 channel に解決する。0 件または複数件なら推測せず BLOCKED: channel contract missing or ambiguous。
  2. required reviewer ごとに、contract が指定する版(構造凍結稿または完成稿)への report が あることと、blocking finding が処分済み(反映、または著者裁定で不採用)であることを、 処分記録と照合して確認する。report が無ければ FAIL。
  3. contract の deterministic checks を実行または証跡照合する。秘密・個人 path・未サニタイズの 生ログは全公開物の共通 blocker とする。媒体固有 validator は contract の command を使う。
  4. contract がその channel にタイトル選択を求めるなら、著者が本文の最後の構造変更より後にタイトルを選択済みか確認する。
  5. prose を再レビューせず、証拠付きで 1 つの verdict を返す。

Verdict

  • PASS — contract の全 blocker が満たされ、著者の公開 GO に渡せる
  • FAIL — 必須 report / check / title decision に未解決項目がある
  • BLOCKED — channel contract が無い、曖昧、または named artifact を確認できない
# Quality Gate Result
Artifact: <path>
Channel: <channel>
Verdict: PASS | FAIL | BLOCKED

## Evidence
- [pass|fail|missing] <contract item>: <source or command result>

## Required next action
- <one concrete action, or "author publication GO">

Boundaries

  • 本 skill は reviewer を起動せず、reviewer の判断を上書きしない。
  • 受け入れ条件は現在の contract と現在稿の証跡だけ。
  • paper は paper-ecosystem(~/MyAI_Lab/paper-lab 常駐)、README は readme-writer の専用 gate を使う。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.