pr-pipeline-tauceti
Use when a Lean or Mathlib-style change is intended for a TauCetiProject/TauCeti pull request, including local readiness, PR drafting, review iteration, or current-head review checks.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pr-pipeline-tauceti
- description
- Use when a Lean or Mathlib-style change is intended for a TauCetiProject/TauCeti pull request, including local readiness, PR drafting, review iteration, or current-head review checks.
02 资源文件 2
- 参考文档references/tauceti-contract.md3.2 KB
- 脚本scripts/local-review.sh3.8 KB
03 SKILL.md 正文
<SUBAGENT-STOP> If dispatched for one bounded PR stage, execute that stage only and return its evidence. </SUBAGENT-STOP>
Input: checkout, diff/context, write scope. Read references/tauceti-contract.md; the live AGENTS.md overrides it and requests. Empty diff: roadmap-only; verify target/claim, return evidence/blockers, then stop read-only: no lean-prepare-pr, Lean/build, PR draft, branch, PR, or write. If formalization is needed, using-leanpowers completes first; REQUIRED SUB-SKILL: one lean-prepare-pr on exact snapshot; validate; rerun if stale. Use lean-apply-feedback.
- Resolve checkout/remote/base/head/branch/in-flight. Read
AGENTS.md,README.md,COORDINATION.md, PR template, andTauCetiRoadmap. New math needs an exact merged-roadmap target and a live claim: an intention issue the requesting human filed, assigned to their login and unexpired (TauCetiRoadmap README §Coordinating work; body getsCloses TauCetiProject/TauCetiRoadmap#N), or our worker leaserefs/tauceti-claims/author/<focus>/<id>. None, or any live claim by another owner: stop. Upstream both are cooperative; the stop is local policy. Maintenance names its area or usesRoadmap: noneonly for genuinely general, cross-cutting, infrastructure, or dependency work. - Keep one topic; no stacked PRs, drafts included: a dependent opens only after its prerequisite lands on
main. Branches prepared ahead on the human's fork may build on each other. Before opening, rebase onto currentmain(git rebase --onto <upstream>/main <prerequisite-head> <branch>), verify the diff againstmainis this one topic, and redo steps 3 and 5. Inspect paths; reuse Tau Ceti/Mathlib first. List each rule ofAGENTS.md§The rules of the repo at the observed commit with its check; reject violations and accidental human-owned edits. Preserve intentionalscripts/,.github/, or lakefile changes and stop for human review; only documented pin files may move forward. Code from another pin goes throughlean-upgradeto TauCeti's current pin first. - Validate the one
lean-prepare-prresult: paths/diff, style/review/fidelity/verification receipts, checks, linter,lake build, and axiom/full-type inspection. Record commit, pins, failures, and stale evidence; green build is not semantic or roadmap approval. - Draft the live PR body with one standalone
Roadmap:line, result, receipts, scope, limits. Add<!--tauceti-target:v1 {"focus":"<area>","id":"<canonical-target-id>"}-->for roadmap work. The newest literaltauceti-scoreboardcomment must containtauceti-meta:v1.head_shaexactly equal to the actual PR head; otherwise unreviewed. - Before the first push and every fix push: the commit to push is a new snapshot, so refresh step 3's receipts and build/lint/axiom checks on it, then run
scripts/local-review.sh <checkout> <title-and-body-file>(minutes; run in background). It applies TauCetiReview's own engine and current-mainrubrics to that commit and posts nothing; exit 0 means every rubric approved, 1 findings, 2 or 3 the engine could not run. Record head and TauCetiReview SHA. Fix findings vialean-apply-feedback, commit, rerun: at most three fix rounds after the first run. If any rubric is still red, or a finding can be shown wrong, stop: give the human the head SHA, red rubrics, scoreboards and options (more rounds, open as is, drop). Pushing a head with a red local rubric needs a fresh explicit instruction from the human naming that head; earlier or general authorization does not cover it. Upstream review is not automatic at present (TauCeti README §Review), so opening does not guarantee a verdict. If the engine cannot run, judge the diff once per rubric file (after_common.md) at that SHA, verdict plus evidence. Common misses to check: provenance only in the PR body rather than the module docstring (lean-prepare-pr); hypotheses stronger than the proof uses; inlineshowwhere a namedhavebelongs; general lemmas in a specialised file. Then stop at readiness unless remote mutation is explicitly authorized now (using-taucetipowers: authorization). Record the observed head. New branch:git push --force-with-lease=<branch>: <remote> HEAD:<branch>. Existing branch:git push --force-with-lease=<headRefName>:<observed_oid> <remote> HEAD:<headRefName>. A stale lease means re-observe, never plain/force push. Rungh pr createonly after body approval. - After push, watch CI and the newest scoreboard for the exact head (
tauceti-review <PR>is the read-only rerun;--postonly when authorized). No scoreboard for the current head means unreviewed: run read-onlytauceti-review <PR>and report it to the human. Done means CI green and every rubric green for the current head. Findings go throughlean-apply-feedback: fix by pushing through step 5 again; reply in the rubric thread (when authorized) only to contest a finding that is wrong. Stop there: merging, closing and de-duplicating are the repo's CI and bors, never the agent; never--admin. A bors merge shows the PR as CLOSED, titled[Merged by Bors] - …, with nomergedAt; confirm the commit onmain. Points raised after merge go in a follow-up PR.
Return paths/diff, claim evidence, receipts, rubric-gate result with TauCetiReview SHA, draft body, remote actions, review status, and blockers.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code