name	pr-workflow-fast
description	Fast, consistent branch/PR workflow with explicit change-type quality gates and concise evidence-first PR descriptions.

PR Workflow Fast

Type: User-Invocable, Agent-Invocable LLM Access: Yes Purpose: Efficient branch/PR workflow with minimal ceremony and explicit quality gates.

Use This Skill When

You want a branch + PR quickly.
You need consistent, reviewable PR descriptions from oracle/test outputs.
You want checks selected by change type.

Branch Policy

Branch prefix: codex/.
Name pattern: codex/<scope>-<short-goal>.
Keep PR scope narrow and mergeable.
When .jj is present, docs/guides/JJ_AI_CHANGE_STACK.md may be used for local change-stack curation before pushing the Git branch.

Change-Type Gates

Docs/styles only (.md, styles/*.yaml):
- syntax sanity + targeted rendering/oracle checks
Rust-touching (.rs, Cargo.toml, Cargo.lock):
- cargo fmt --check ← use --check, never bare cargo fmt (fmt is a fix, not a gate)
- cargo clippy --all-targets --all-features -- -D warnings
- cargo nextest run (fallback: cargo test)
- Gate must pass before the first push. If gate fails after builder work, fix + amend the unpushed commit (amend is allowed on unpushed commits), re-verify, then push. Never push a failing commit and follow up with a cleanup commit.
- Every commit on the branch must individually be gate-clean.
Hot path/perf claims:
- benchmark baseline/after via ./scripts/bench-check.sh

If Gate Fails After Push

If you discover a gate failure after pushing, squash + force-push (git push --force-with-lease) rather than adding a cleanup commit. Requires CONFIRM (critical action).

PR Body Template

Summary: what changed and why.
Scope: files and affected workflows.
Validation: exact commands run + key results.
Risk: potential regressions and mitigation.
Follow-ups: non-blocking next steps.

Efficiency Rules

One oracle snapshot per iteration unless structure changes materially.
Stop at target metric; avoid unbounded polish loops.
Escalate to planner when style-only fixes stall.
Prefer smallest diff that achieves gate pass.

Merge Readiness Checklist

Checks passed for touched change type.
PR body includes objective evidence.
No unresolved high-severity findings.

Más de este repositorio

mismo repositorio

style-migrate-enhance

citum/citum-core

High-throughput migration waves converting priority parent CSL 1.0 styles to Citum with repeatable before/after metrics and migration-engine gap recommendations. Fidelity is the hard gate.

2026-07-0230

style-qa

citum/citum-core

Standardized QA gate for style work. Verifies fidelity, SQI drift, formatting defects, and regression surface. Produces approve/reject verdict with numbered findings.

2026-07-0230

style-tune

citum/citum-core

Iterative LLM hand-tuning loop for embedded-core styles. Drives a style to 100% fidelity and clean SQI. Both are hard gates. Seeded from migrate evidence, not from the converter output as a terminal deliverable.

2026-07-0230

migrate-research

citum/citum-core

Autonomous research loop for Citum migration fidelity gaps and converter-focused Rust fixes.

2026-07-0230

style-evolve

citum/citum-core

Single human-facing command for all Citum style work. Use whenever someone asks to fix, improve, convert, create, or tune a citation style. Routes to upgrade, migrate, create, or tune. Always use this rather than calling internal skills directly.

2026-06-2430

style-evolve

citum/citum-core

Public entrypoint for Citum style work. Activate on: 'upgrade', 'migrate', 'create', 'tune', any style authoring request, or any request to fix/improve/convert a Citum or CSL citation style. Route to the shared workflow docs and internal roles.

2026-06-2430

PR Workflow Fast

Type: User-Invocable, Agent-Invocable LLM Access: Yes Purpose: Efficient branch/PR workflow with minimal ceremony and explicit quality gates.

Use This Skill When

You want a branch + PR quickly.

You need consistent, reviewable PR descriptions from oracle/test outputs.

You want checks selected by change type.

Branch Policy

Branch prefix: codex/.

Name pattern: codex/<scope>-<short-goal>.

Keep PR scope narrow and mergeable.

When .jj is present, docs/guides/JJ_AI_CHANGE_STACK.md may be used for local change-stack curation before pushing the Git branch.

Change-Type Gates

Docs/styles only (.md, styles/*.yaml):

syntax sanity + targeted rendering/oracle checks

Rust-touching (.rs, Cargo.toml, Cargo.lock):

cargo fmt --check ← use --check, never bare cargo fmt (fmt is a fix, not a gate)
cargo clippy --all-targets --all-features -- -D warnings
cargo nextest run (fallback: cargo test)
Gate must pass before the first push. If gate fails after builder work, fix + amend the unpushed commit (amend is allowed on unpushed commits), re-verify, then push. Never push a failing commit and follow up with a cleanup commit.
Every commit on the branch must individually be gate-clean.

Hot path/perf claims:

benchmark baseline/after via ./scripts/bench-check.sh

If Gate Fails After Push

If you discover a gate failure after pushing, squash + force-push (git push --force-with-lease) rather than adding a cleanup commit. Requires CONFIRM (critical action).

PR Body Template

Summary: what changed and why.

Scope: files and affected workflows.

Validation: exact commands run + key results.

Risk: potential regressions and mitigation.

Follow-ups: non-blocking next steps.

Efficiency Rules

One oracle snapshot per iteration unless structure changes materially.

Stop at target metric; avoid unbounded polish loops.

Escalate to planner when style-only fixes stall.

Prefer smallest diff that achieves gate pass.

Merge Readiness Checklist

Checks passed for touched change type.

PR body includes objective evidence.

No unresolved high-severity findings.