quick-fix
Skill2 starsChanged 9 months agoApache-2.0View on GitHub
Auto-suggest fixes for common pre-commit and pattern compliance issues. Or with specific error context: This skill can be suggested by hooks when failures occur: When pre-commit fails, a hook could: When pattern compliance fails:
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
When the task doesn't match this skill's scope -- check related skills
- Distinctive: line 14
When a more specialized skill exists for the specific task
- Distinctive: line 18
When pre-commit hook fails with lint errors
- Distinctive: line 19
When pattern compliance check fails
- Distinctive: line 20
When TypeScript type errors occur
- Distinctive: line 86
When pre-commit fails, a hook could:
- Distinctive: line 94
When pattern compliance fails:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
quick-fix Skill
Auto-suggest fixes for common pre-commit and pattern compliance issues.
When NOT to Use
- When the task doesn't match this skill's scope -- check related skills
- When a more specialized skill exists for the specific task
When to Use
- When pre-commit hook fails with lint errors
- When pattern compliance check fails
- When TypeScript type errors occur
- For quick resolution of common blocking issues
What It Does
- Parse Error Output
- Reads the failed check output
- Categorizes errors by type and severity
- Identifies auto-fixable vs manual issues
- Generate Fix Suggestions
- ESLint: Suggests
npm run lint -- --fixfor auto-fixable issues - Prettier: Runs lint-staged to auto-format
- Pattern compliance: Shows specific line changes needed
- TypeScript: Suggests type annotations or fixes
- ESLint: Suggests
- Apply Auto-Fixes
- Can run
npm run lint -- --fixautomatically - Stages fixed files for commit
- Re-runs checks to verify
- Can run
Usage
/quick-fixOr with specific error context:
/quick-fix [paste error output]Common Fix Patterns
ESLint Errors
| Error | Auto-Fix | Command |
| Missing semicolons | Yes | npm run lint -- --fix |
| Unused imports | Yes | npm run lint -- --fix |
| Quote style | Yes | npm run lint -- --fix |
| Complex functions | No | Manual refactor needed |
Pattern Compliance
| Pattern | Issue | Fix |
| Direct Firestore | Use repository | Wrap in repository method |
| Console.log | Use logger | Replace with logger.debug() |
| Hardcoded paths | Use config | Move to config file |
TypeScript
| Error | Fix |
| Missing type | Add explicit type annotation |
| Any usage | Replace with specific type |
| Null check | Add optional chaining or null check |
Hook Integration
This skill can be suggested by hooks when failures occur:
Pre-commit Failure Hook (proposed)
When pre-commit fails, a hook could:
- Capture the error output
- Suggest
/quick-fixwith context - Offer auto-fix for known patterns
Pattern Check Failure
When pattern compliance fails:
- Show specific file and line numbers
- Suggest code changes inline
- Offer to apply fix
Output Format
/quick-fix Results
==================
Found 3 issues:
1. ESLint: Unused import (AUTO-FIXABLE)
File: src/components/Button.tsx:5
Fix: Remove `import { useState } from 'react'`
Command: npm run lint -- --fix
2. Pattern: Direct Firestore access (MANUAL)
File: src/services/user.ts:42
Issue: `db.collection('users')` should use repository
Fix: Use `userRepository.find()` instead
3. TypeScript: Missing return type (AUTO-FIXABLE)
File: src/utils/format.ts:10
Fix: Add `: string` return type
Auto-fix available for 2 issues.
Run: npm run lint -- --fix && npx tsc --noEmit
Apply auto-fixes? [Y/n]Related
- Pre-commit hook - Runs lint, patterns, tests
- scripts/check-pattern-compliance.js - Pattern checker
- eslint.config.mjs - ESLint configuration
Version History
| Version | Date | Description |
| 1.0 | 2026-02-25 | Initial implementation |
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- gittower/git-flow-next★ 458same name
- danielvm-git/bigpowers★ 286same name
- charliehzm/medharness★ 85same name
- DailybotHQ/deepworkplan-website★ 15same name
- sumulige/sumulige-claude★ 2same name
- iabhisekbosepm/claude-god-setup★ 1same name
- Nexus-Organization-Infosec/ClaudeSkills★ 1same name
- SgtPooki/skills★ 1same name
- acevinh/claude-skills★ 0same name
- AI-Degen-69/issue-to-pr-skills★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use security-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
In this repository81 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- find-skillsSkill
- add-debtSkill
- alertsSkill
- analyzeSkill
- artifacts-builderSkill
- audit-agent-qualitySkill
- audit-aggregatorSkill
- audit-ai-optimizationSkill
- audit-codeSkill
- audit-comprehensiveSkill
- audit-documentationSkill
- audit-engineering-productivitySkill
- audit-enhancementsSkill
- audit-healthSkill
- audit-performanceSkill
- audit-processSkill
- audit-refactoringSkill
- audit-securitySkill
- brainstormSkill
- checkpointSkill
- code-reviewerSkill
- comprehensive-ecosystem-auditSkill
- content-research-writerSkill
- convergence-loopSkill
- create-auditSkill
- data-effectiveness-auditSkill
- debt-runnerSkill
- decrypt-secretsSkill
- deep-planSkill
- deep-researchSkill
- developer-growth-analysisSkill
- doc-ecosystem-auditSkill
- doc-optimizerSkill
- docs-maintainSkill
- document-analysisSkill
- ecosystem-healthSkill
- Excel AnalysisSkill
- find-skillsSkill
- frontend-designSkill
- gh-fix-ciSkill
- github-healthSkill
- health-ecosystem-auditSkill
- hook-ecosystem-auditSkill
- market-research-reportsSkill
- mcp-builderSkill
- media-analysisSkill
- multi-ai-auditSkill
- pre-commit-fixerSkill
- pr-ecosystem-auditSkill
- pr-retroSkill
- pr-reviewSkill
- recallSkill
- repo-analysisSkill
- repo-synthesisSkill
- script-ecosystem-auditSkill
- session-beginSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

