no-mistakes

Validate committed code changes through review, test, lint, and CI pipelines.

2.3k|190|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/mnemosyne-oss/mnemosyne --skill no-mistakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-mistakes
Source: https://github.com/mnemosyne-oss/mnemosyne/tree/main/.agents/skills/no-mistakes
Command: npx skills add https://github.com/mnemosyne-oss/mnemosyne --skill no-mistakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely validate code changes before they are pushed upstream, reducing regressions, missed review steps, and brittle manual release checks.

Core Features & Use Cases

  • Task-aware validation: Handles either validate-only runs for already committed work or task-first runs where the assistant must make the change first.
  • Branch and commit safety: Requires committed work on a feature branch and preserves unrelated uncommitted changes.
  • Pipeline-driven review: Coordinates intent, review, testing, linting, documentation, push, PR, and CI decisions through the no-mistakes workflow.
  • Use case: Ask it to implement a fix and then validate it end to end, or to gate an existing commit before it reaches upstream.

Quick Start

Use the no-mistakes skill to validate my committed changes and report the result.

Frequently Asked Questions about no-mistakes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate committed code changes before pushing to upstream?

Validating committed changes before an upstream push requires running an intent-driven pipeline that coordinates review, testing, linting, documentation, PR creation, and CI gates on your feature branch.

Can I automate code review, linting, and CI gating for a feature branch?

Yes, you can automate code review, linting, and CI gating for a feature branch through a pipeline-driven workflow that manages gate decisions, review outcomes, auto-fixes, and rerun workflows before release.

How do I run a validate-only check on an existing feature branch commit?

To run a validate-only check on an existing commit, use a branch-aware execution mode that evaluates already committed work through the review, test, and lint pipeline without requiring a new task-first implementation.

Does the validation pipeline preserve uncommitted changes when running on a feature branch?

Yes, the validation pipeline preserves unrelated uncommitted changes by requiring committed work on the feature branch, ensuring local modifications remain intact while the review and CI gates execute.

What is an intent-driven code review and validation pipeline?

An intent-driven code review and validation pipeline is a process that coordinates testing, linting, documentation, push, PR, and CI decisions based on the specific intent passed to the workflow, ensuring safe history and gate management.

How do I handle CI gate failures and auto-fix requests during a pull request validation?

To handle CI gate failures during pull request validation, the workflow supports gate response handling, allowing you to manage auto-fix approvals, skip checks, query status, or trigger reruns within the branch-aware execution.