Run any Skill in Manus with one click

Get Started

fix-precommit

Stars9

Forks0

UpdatedApril 19, 2026 at 22:22

Run pre-commit hooks and fix any errors they report

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ExplorerFreda

ExplorerFreda/fskills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	fix-precommit
description	Run pre-commit hooks and fix any errors they report

Run the pre-commit hooks and fix any errors they report.

Steps:

Run uv run pre-commit run --all-files and capture the output.
Read the output carefully. Identify every file and error flagged.
For each error, open the relevant file(s) and apply the necessary fixes:
- Flake8 violations: fix the specific line(s) reported (line length, unused imports, whitespace, etc.)
- Formatter changes (e.g. ruff-format, black): apply the formatting the hook expects
- Any other hook failures: follow the specific guidance in the hook output
After fixing all issues, re-run uv run pre-commit run --all-files to verify all hooks pass.
If new errors appear in the re-run, repeat the fix-and-verify cycle until the run is fully clean.

Important rules while fixing:

Follow the project style: single quotes for string literals, double quotes only for docstrings.
Do not add unnecessary changes beyond what the hooks require.
Do not commit anything.

More from this repository

same repository

generate-report

ExplorerFreda/fskills

Generate a styled HTML report from experiment results following the house design system. Usage: /generate-report --results <path> --out <folder> [additional instructions]

2026-04-229

expand-writing

ExplorerFreda/fskills

Expand a rough draft into polished technical prose, calibrated to a described audience. Usage: /expand-writing --out <path> --audience "<desc>" <input-path-or-inline-text>

2026-04-219

review-paper

ExplorerFreda/fskills

Review a scientific paper (LaTeX source) against the CompLING house style for writing and math typesetting. Usage: /review-paper [path] [additional instructions]

2026-04-209

ensure-english-consistency

ExplorerFreda/fskills

Ensure all text and code files in the repository follow a single region's English convention (US, CA, or UK). Usage: /ensure-english-consistency <US|us|CA|ca|UK|uk> [additional instructions]

2026-04-209

inspect-data

ExplorerFreda/fskills

Inspect a data file (JSONL, JSON, Parquet, or HDF5) or a HuggingFace dataset to understand its structure. Usage: /inspect-data <file_path_or_dataset_id> [additional instructions]

2026-04-209

name	fix-precommit
description	Run pre-commit hooks and fix any errors they report

Run the pre-commit hooks and fix any errors they report.

Steps:

Run uv run pre-commit run --all-files and capture the output.
Read the output carefully. Identify every file and error flagged.
For each error, open the relevant file(s) and apply the necessary fixes:
- Flake8 violations: fix the specific line(s) reported (line length, unused imports, whitespace, etc.)
- Formatter changes (e.g. ruff-format, black): apply the formatting the hook expects
- Any other hook failures: follow the specific guidance in the hook output
After fixing all issues, re-run uv run pre-commit run --all-files to verify all hooks pass.
If new errors appear in the re-run, repeat the fix-and-verify cycle until the run is fully clean.

Important rules while fixing:

Follow the project style: single quotes for string literals, double quotes only for docstrings.
Do not add unnecessary changes beyond what the hooks require.
Do not commit anything.