no-mistakes is a local Git proxy that validates changes in an isolated worktree before forwarding a push to the real remote and opening a pull request. It is for developers and coding agents that want automated checks, safe fixes, CI repair, and human review before changes are published.
Borrowing it
Nothing to install: this file belongs to kunchenguid/no-mistakes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kunchenguid/no-mistakes/main/.agents/skills/pipeline-review-and-agents/SKILL.mdgit clone --depth 1 https://github.com/kunchenguid/no-mistakesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kunchenguid/no-mistakes/pipeline-review-and-agents)<a href="https://agentmods.dev/skills/kunchenguid/no-mistakes/pipeline-review-and-agents"><img src="https://agentmods.dev/badge/skills/kunchenguid/no-mistakes/pipeline-review-and-agents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kunchenguid/no-mistakes/pipeline-review-and-agents"><img src="https://agentmods.dev/badge/skills/kunchenguid/no-mistakes/pipeline-review-and-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium System Prompt Leakage · line 65 Skill contains patterns that could indirectly extract system prompts through rephrasing, translation, summarization, or side-channel techniques.Fix: Guard against indirect extraction by refusing to summarize, translate, or rephrase system instructions. Add explicit anti-extraction clauses.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.04704 |
| Opus 5 | $0.00014 | $0.02352 |
| Sonnet 5 | $0.00006 | $0.00941 |
| Haiku 4.5 | $0.00003 | $0.00470 |
Grade A, and why
pipeline-review-and-agents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review-Loop Agent Sessions (internal/pipeline/sessions.go)
- Per run, the review loop keeps ONE durable fixer session across review-fix turns, and EVERY review turn (initial review and every full rereview) runs session-free. A rereview certifies fixes implementing the previous review turn's findings, so resuming any review session seats the prescriber as certifier - the mechanism that let one fix round ship wrong code plus the test blessing it with zero findings. Cross-round review context travels only in the explicit sanitized round history; the fixer session is never lent to review turns, no other step uses sessions, and sessions are keyed strictly by run. The rereview prompt reframes fix-round changes as pipeline-authored code under the author-grade adversarial standard (
fixRoundProvenanceClause); the same clause is emitted on a later run's initial review when a persisted uncertified range is bound. Prior findings, fix summaries, and same-round tests are claims, not evidence. - Fail-safe rules: unsupported adapter runs cold; a failed fixer resume drops the identity and re-runs the same turn in a fresh fixer session, never skipping the turn; a cancelled ctx gets no fallback retry;
session_reuse: falseforces everything cold. Persistence is minimum metadata only, never prompts or transcripts;SessionRoleReviewerremains only so crash recovery accepts legacy persisted rows, which are never resumed. codex exec resumehas a narrower flag surface thancodex exec, so an unsupported override fails the resume and falls back; the e2e fakeagent must keep parsing both codex argv shapes (extractCodexPrompt).- Regressions:
internal/pipeline/sessions_test.go,internal/pipeline/steps/review_session_test.go(incl.TestReviewLoop_RereviewNeverResumesTheSessionThatPrescribedItsFixes),TestReviewStep_RereviewTreatsFixRoundsAsPipelineAuthoredCode,internal/agent/session_test.go.
Recorded Human Decisions on Findings
- Approve, skip, and abort each record
selected_finding_ids = "[]"plusselection_source = user_declinedon a gated round with findings (executor.gorecordDeclinedRound,db.SetStepRoundDeclined); a round with no findings records no decision. The conditional write must never erase an existing selection. User-facing semantics are owned bydocs/src/content/docs/reference/pipeline-steps.md. - A decline is stored as the COMPLEMENT of the selection, never as its own list;
declinedFindingLinesderives it and deliberately excludesauto_fixselections, whose complement is findings still awaiting a decision (rendered underauto_fix_left_unselected, which carries no do-not-re-report instruction). roundHistoryPromptSection(internal/pipeline/steps/round_history.go) now carries three parts: this step's rounds, this run's OTHER steps' decisions, and earlier runs' decisions on this branch (bound per step bypipeline.BindBranchDecisions, unlike review-onlyBindUncertifiedPipelineRange). Nothing clears branch decisions - a completed review deletes the uncertified range, which is why that channel could not carry a decision forward, but approving a gate IS the decision. The prompt states that a recorded decision SUPERSEDES the user-intent wording.- Deliberately ADVISORY and fail-open: no step is blocked and no commit is gated, so an agent may still re-raise a declined finding when the code genuinely changed. There is no reversion detector;
assertPipelineHeadContinuityandassertReviewApprovedPushHeadremain lineage-only.ci_fix.gocomposes the section like the other fix-capable steps - beforeuserIntentPromptSection, because the run's frozen intent always predates a later gate's decision - so a CI repair sees the decision an earlier gate, an earlier run on this branch, or its own gate recorded (internal/pipeline/steps/ci_decision_history_test.go).rebase.gostill builds its prompt withoutroundHistoryPromptSection. - Regressions:
TestExecutor_GateResolutionsWithoutASelectionRecordTheDecline,TestExecutor_GateResolutionWithNoFindingsRecordsNoDecision,TestExecutor_FixResolutionStillRecordsAUserSelection,internal/db/round_decisions_test.go,TestDeclinedFindingReachesALaterStepInTheSameRun,TestDeclinedFindingReachesALaterRunOnTheSameBranch,TestCompletedReviewDoesNotClearBranchDecisions,TestAutoFixComplementIsNeverPresentedAsAUserDecision.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago Changed · +1 lines 8e12782f6efd
- 6d ago Changed 74e226bc7a1c
- 8d ago Changed · +18 lines 3e4ed86da205
- 13d ago First seen · 72 lines · 28 tokens per session scan A a8d3e02f7bd6
pipeline-review-and-agents is a skill published in the GitHub repository kunchenguid/no-mistakes (8,416 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 4,704 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…