Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

intake

Étoiles0

Forks0

Mis à jour7 juillet 2026 à 00:34

Convert owner-filed GitHub issues into the tasks-file backlog via PR (project specifics from the profile). Classifies each unmapped issue (no task ID in title, unreferenced by any live tasks file) into spec work / repo-maintenance / bug / duplicate / underspecified, screens it against the constitution, drafts the backlog entry on a branch, and lands it as a PR the owner ratifies by merging. Use when the user says "intake", "run intake", "convert issue

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Chris-Graffagnino

Chris-Graffagnino/creance

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

next-task

Chris-Graffagnino/creance

Start the next unblocked task in the build with full ceremony (project specifics from the profile). Use when the user says "next task", "work the next task", "continue the build", "what's next", or names a task ID to implement. Picks the task, opens the issue, cuts the branch, implements with tests, verifies, and runs review — stopping at PR (review mode).

2026-07-110

pr-review

Chris-Graffagnino/creance

Verified review of an open PR — fetch the diff AND every inline reviewer comment (including bot/automated inline findings), verify each finding against current source (file:line) and run the project's checks where relevant, then post one structured, severity-ranked review comment. Never declares "no findings" until every inline comment is adjudicated and every finding is grounded to source. Project specifics from the profile. Use when the user says "review PR

2026-07-090

review-response

Chris-Graffagnino/creance

Resolve the reviewer findings on your own open PR end-to-end — fetch the diff AND every inline comment (human and bot/automated), verify each against current source (file:line), apply the minimum scoped fix with red→green proof, RE-RUN the §7 gate on the fix (maker ≠ checker — a fix is not self-certified), reply to every comment, and confirm the head is green. Never merges — stops for the owner. Pushes fixes and posts replies (the write posture pr-review lacks). Project specifics from the profile. Use when the user says "address the reviewer comments on PR

2026-07-090

triage

Chris-Graffagnino/creance

Morning read-only triage heartbeat for the build (project specifics from the profile). Reads the tasks file, git history, and GitHub issues/PRs, then writes a fresh state snapshot to the out-of-repo inbox. Surfaces the next unblocked task, stale checkboxes, open PRs needing review, blocked/owner items, and upcoming constitution risks. Use when the user says "triage", "morning triage", "what's the state of the build", or when fired on a schedule. NEVER edits code, opens issues/PRs, or commits.

2026-07-070

maker-eval

Chris-Graffagnino/creance

Run the standing maker-eval corpus (project specifics from .claude/PROJECT.md). Re-scores the MAKER — the generation path that writes the code — against the frozen golden-task corpus + per-task rubrics with the pinned judge, after a maker-behavior fingerprint change (the maker model resolution OR an instruction/runtime surface that shapes its output, not the model table alone) or on the weekly schedule. The maker analog of auditor-liveness for the reviewers. Executes each corpus task as a [headless run] of the maker, scores the output with a read-only [reviewer]-style judge, and APPENDS an observe-only record + transcript packet per task to the fenced eval channel — which never feeds a gate outcome, tier assignment, or gate semantics (P5). Use when the user says "maker eval", "run the maker corpus", "eval the maker", "re-score the maker", when triage flags MAKER-EVAL-STALE, or on the weekly schedule. Read-and-append only — never edits the frozen instrument, never gates, never merges.

2026-07-030

auditor-liveness

Chris-Graffagnino/creance

Run the standing auditor-liveness corpus (project specifics from .claude/PROJECT.md). Re-confirms each judgment auditor (acceptance / constitution / contract / spec-quality) still catches its planted-violation fixtures and still passes its clean fixtures, after a reviewer-spec edit or model drift — the model-driven analog of guard.test.sh, promoted from the one-time P-RV probe. Dispatches the auditors READ-ONLY and report-only against materialized plants, compares each verdict to the corpus's expected verdict, and records an OBSERVE-ONLY outcome that never feeds gate outcomes, tier assignment, or gate semantics (P5). Use when the user says "auditor liveness", "run the auditor corpus", "re-confirm the auditors", when triage flags CORPUS-STALE, or on the weekly schedule. Read-and-report only — never edits a reviewer spec, never gates, never merges.

2026-07-030

/intake — Claude Code binding

The workflow logic is runtime-neutral and lives in .claude/workflow/intake.md — read that file now and execute it. Mapping of its abstract [roles]:

Neutral role

Claude Code mechanism

[workflow] (this one)

this skill; arguments (e.g. specific issue numbers) arrive in the invocation text

[reviewer] / §7 gate

as bound in .claude/skills/next-task/SKILL.md (the gate on the conversion PR runs exactly as next-task's does, [orchestrated run] included)

[comment marker]

the footer line defined in .claude/skills/next-task/SKILL.md → "The [comment marker] concrete form" (the single copy) — on every gh issue comment / gh pr comment body this workflow posts

[environment block]

.claude/skills/next-task/SKILL.md → "This environment's concrete forms" (the single copy — multi-line bodies via UTF-8 temp file + --body-file, gh PATH fallback)

[headless run]

claude -p "/intake"

tracker reads/writes

gh issue list/view (read), gh issue comment / gh issue edit --title / gh issue edit --add-label (additive writes only — never gh issue close, never a merge)

Write posture per the workflow doc: repo edits happen only on an intake branch (the PreToolUse guard blocks base-branch edits deterministically); the conversion PR carries no closing keyword for the source issue; merge is the owner's alone.

Profile read — packet first (spec 007 US3.AC3). Read .claude/PROJECT.compact.md by default for the routing facts (tasks-file paths, task-ID blocks, title/branch conventions, required check — drift-checked by .claude/hooks/compact-packet-drift.sh in CI). Escalate to the full .claude/PROJECT.md explicitly — say you are escalating and why — when a classification needs a fact the packet deliberately omits (an invariant's full text, architecture boundaries, blocked-task detail); the full profile stays the source of truth.

/intake — Claude Code binding

The workflow logic is runtime-neutral and lives in .claude/workflow/intake.md — read that file now and execute it. Mapping of its abstract [roles]:

Neutral role

Claude Code mechanism

[workflow] (this one)

this skill; arguments (e.g. specific issue numbers) arrive in the invocation text

[reviewer] / §7 gate

as bound in .claude/skills/next-task/SKILL.md (the gate on the conversion PR runs exactly as next-task's does, [orchestrated run] included)

[comment marker]

the footer line defined in .claude/skills/next-task/SKILL.md → "The [comment marker] concrete form" (the single copy) — on every gh issue comment / gh pr comment body this workflow posts

[environment block]

.claude/skills/next-task/SKILL.md → "This environment's concrete forms" (the single copy — multi-line bodies via UTF-8 temp file + --body-file, gh PATH fallback)

[headless run]

claude -p "/intake"

tracker reads/writes

gh issue list/view (read), gh issue comment / gh issue edit --title / gh issue edit --add-label (additive writes only — never gh issue close, never a merge)