path-tactics

Automate RwEq proof boilerplate in Lean using path tactics.

1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/Arthur742Ramos/ComputationalPathsLean --skill path-tactics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: path-tactics
Source: https://github.com/Arthur742Ramos/ComputationalPathsLean/tree/main/.claude/skills/path-tactics
Command: npx skills add https://github.com/Arthur742Ramos/ComputationalPathsLean --skill path-tactics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces boilerplate in RwEq proofs by leveraging ComputationPaths path tactics to automate common goals (path_simp, path_auto, path_normalize) and present calc-based proofs with clear structure.

Core Features & Use Cases

  • Automated RwEq steps: Use path_auto for stand-alone goals dominated by groupoid laws, associativity, and cancellations.
  • Cleanup and simplification: Use path_simp inside larger proofs to finish near-completion steps.
  • Normalization for definitional mismatches: Use path_normalize when sides differ by definitional parenthesization.
  • Readable calc-based proofs: Encourages calc-chains with explicit ÷ steps for clarity.

Quick Start

In a Lean proof, import the tactic module and try path_auto to discharge simple RwEq goals. If the goal is stuck due to definitional mismatch, run path_normalize; for minor cleanups, apply path_simp. You can structure proofs with calc and the ÷ notation, finishing with path_simp or path_auto as needed.

Frequently Asked Questions about path-tactics

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

FAQPage Schema
How do I automate RwEq proofs in Lean?

RwEq proofs in Lean can be automated using path tactics like path_auto, path_simp, and path_normalize from the ComputationalPaths library. path_auto discharges goals dominated by groupoid laws and cancellations; path_simp handles cleanup in larger proofs; path_normalize resolves definitional mismatches between sides.

When should I use path_auto vs path_simp in Lean proofs?

Use path_auto for standalone RwEq goals involving groupoid laws, associativity, and cancellations. Use path_simp for minor cleanup steps inside larger proofs that are near completion, or path_normalize when proof sides differ only by definitional parenthesization.

Can I structure RwEq proofs with calc notation in Lean?

Yes, path tactics support calc-style proof chains with explicit ÷ notation for clarity. You can write calc-based proofs and finish them with path_simp or path_auto, producing readable, step-by-step RwEq solutions.

What types of Lean proof goals does path_auto handle?

path_auto handles standalone RwEq goals involving groupoid laws, cancellations, associativity reshaping, and longer proofs requiring unit-law cleanup and finalization steps through the ComputationalPaths.Path.Rewrite.PathTactic library.

Do I need additional setup to use path tactics in Lean?

You need to import the path tactic module from ComputationalPaths.Path.Rewrite.PathTactic library. After importing, path_auto, path_simp, and path_normalize are available for RwEq goals without additional configuration.

How do I handle definitional mismatches in RwEq proofs?

When RwEq proof sides differ only by definitional parenthesization, apply path_normalize to resolve the mismatch and normalize both sides to a common form.