Source
Open the upstream repository and check maintainers, README scope, examples, and recent activity.
hook
Agent readyRuff pre-commit
Review before use
pre-commit integration for the Ruff Python linter and formatter. GitHub metadata was checked on 2026-06-27; the listed license is no-fee and permissive for review, evaluation, and responsible reuse.
Source review
License
Confirm Apache-2.0 terms fit your project and retain notices when required.
Install behavior
Read commands before running them and start with a low-risk local workspace.
Verification
Check outputs, safety notes, and policy fit before exposing the resource to agent workflows.
Why use it
Use it when a project needs Python lint and format gates inside a standard hook workflow and the team wants inspectable provenance before adoption.
When to use
- You need Python lint and format gates inside a standard hook workflow.
- The upstream README and license fit the target project.
- You can test the integration on non-production data first.
When not to use
- The hook would run unreviewed shell commands.
- Blocking behavior would stop unrelated developer work.
Agent manifest preview
Use the manifest as structured review context before applying local policy.
{
"schemaVersion": "1.0",
"slug": "ruff-pre-commit",
"title": "Ruff pre-commit",
"kind": "hook",
"summary": "pre-commit integration for the Ruff Python linter and formatter.",
"sourceUrl": "https://github.com/astral-sh/ruff-pre-commit",
"agentAccess": "approved",
"license": {
"spdx": "Apache-2.0",
"allowsClosedSourceUse": true,
"requiresNotice": true,
"noLicenseFee": true
},
"install": {
"steps": [
"Inspect the hook command and arguments.",
"Run it locally on sample changes.",
"Enable it only after expected false positives are understood."
]
},
"outputs": [
"hook result",
"scan finding",
"blocked-change reason"
],
"usage": {
"whyUse": "Use it when a project needs Python lint and format gates inside a standard hook workflow and the team wants inspectable provenance before adoption.",
"whenToUse": [
"You need Python lint and format gates inside a standard hook workflow.",
"The upstream README and license fit the target project.",
"You can test the integration on non-production data first."
],
"whenNotToUse": [
"The hook would run unreviewed shell commands.",
"Blocking behavior would stop unrelated developer work."
],
"safetyNotes": [
"Keep required license notices when redistributing copied source or bundled code.",
"Use dry-run or warn mode first.",
"Keep bypass and rollback steps documented."
]
},
"repository": {
"owner": "astral-sh",
"name": "ruff-pre-commit",
"stars": 1957,
"defaultBranch": "main"
},
"lifecycle": {
"githubUpdatedAt": "2026-06-26T09:45:21Z",
"githubPushedAt": "2026-06-26T06:19:49Z",
"lastVerifiedAt": "2026-06-27T00:00:00.000Z"
}
}