pagekit-run-check

Sterne9

Forks2

Aktualisiert16. April 2026 um 05:14

Validate a PageKit run folder against the logging tiers (fully-logged / summary-logged / artifact-only / incomplete). Wraps scripts/run-check.sh. Use at the end of a run to confirm the fully-logged tier is met before declaring done.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

hnshah

hnshah/pagekit

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	pagekit-run-check
description	Validate a PageKit run folder against the logging tiers (fully-logged / summary-logged / artifact-only / incomplete). Wraps scripts/run-check.sh. Use at the end of a run to confirm the fully-logged tier is met before declaring done.

PageKit — Validate a Run

Wraps scripts/run-check.sh. Reads a run folder and classifies it per ../pagekit/references/run-logging.md. Lists missing files for the next tier up.

Procedure

Run: bash scripts/run-check.sh runs/<run-name>.
If the result is FULLY LOGGED, report success.
If the result is SUMMARY LOGGED or below, list the missing items to the user and propose what to fill in to reach fully-logged.

When to invoke

At the end of any run produced via the pagekit orchestrator skill.
Before treating a run as validation evidence or as a public example.
When picking up an existing run to extend.

Hard rule

Do not declare a run "done" if pagekit-run-check returns anything other than FULLY LOGGED. The whole point of mechanized checks is to stop logging from being the part that gets skipped.

Mehr aus diesem Repository

gleiches Repository

pagekit-claim-check

hnshah/pagekit

Run a skeptical claim-check pass on a PageKit first-page draft, at light/normal/hard severity. Step 07 of the PageKit method. Use after a first-page draft exists and you want to validate it before treating it as publishable. Delegates to the pagekit-claim-checker subagent.

2026-04-179

pagekit-first-page-decision

hnshah/pagekit

Decide which page should exist first for the object, without defaulting to homepage. Step 03 of the PageKit method. Use when the user has a signal doc + message spine and needs to choose the first page, or asks "should this be a homepage?" or "what page should we build first?"

2026-04-179

pagekit-first-page-draft

hnshah/pagekit

Draft the first page from the full PageKit chain. Step 06 of the PageKit method. Use when steps 01-05 are done and you are ready to write the page itself. The draft must respect the anti-slop drafting constraints.

2026-04-179

pagekit-message-spine

hnshah/pagekit

Reduce a PageKit signal doc into a message spine. Step 02 of the PageKit method. Use when the user asks to "reduce this signal to a spine," "build a message spine," or has finished step 01 and is ready for step 02.

2026-04-179

pagekit-page-argument-shape

hnshah/pagekit

Design the page argument shape — what sections the chosen first page should and should not have. Step 04 of the PageKit method. Use when the first-page decision is made and you need a structure for the draft.

2026-04-179

pagekit-proof-map

hnshah/pagekit

Map proof to the chosen first page section by section. Step 05 of the PageKit method. Use after the page argument shape exists and before drafting.

2026-04-179

name	pagekit-run-check
description	Validate a PageKit run folder against the logging tiers (fully-logged / summary-logged / artifact-only / incomplete). Wraps scripts/run-check.sh. Use at the end of a run to confirm the fully-logged tier is met before declaring done.

PageKit — Validate a Run

Wraps scripts/run-check.sh. Reads a run folder and classifies it per ../pagekit/references/run-logging.md. Lists missing files for the next tier up.

Procedure

Run: bash scripts/run-check.sh runs/<run-name>.
If the result is FULLY LOGGED, report success.
If the result is SUMMARY LOGGED or below, list the missing items to the user and propose what to fill in to reach fully-logged.

When to invoke

At the end of any run produced via the pagekit orchestrator skill.
Before treating a run as validation evidence or as a public example.
When picking up an existing run to extend.

Hard rule

Do not declare a run "done" if pagekit-run-check returns anything other than FULLY LOGGED. The whole point of mechanized checks is to stop logging from being the part that gets skipped.