agentleFS
DailybotHQDailybotHQ/deepworkplan-website/.agents/skills/quick-fix/SKILL.md

quick-fix

Skill15 starsChanged 5 months agoMITView on GitHub

Fix small bugs and issues in 1-3 files following existing patterns. Use proactively for simple bug fixes.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects 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.
  • SentrySkill

    security-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

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Does NOT refactor large sections of code

    line 24
  2. Distinctive:

    Does NOT add new features

    line 25
  3. Distinctive:

    Does NOT change architectural patterns

    line 26
  4. Distinctive:

    Does NOT modify more than 3 files

    line 27
  5. Distinctive:

    Does NOT handle security-sensitive code

    line 28
  6. Distinctive:

    Before running this skill, ensure:

    line 49
  7. Distinctive:

    Read the issue description

    line 59
  8. Distinctive:

    Read the affected file(s)

    line 65
  9. Distinctive:

    Follow existing code patterns exactly

    line 72
  10. Distinctive:

    Run validation commands for this repo:

    line 78
  11. Distinctive:

    Escalate to Tier 2: if:

    line 157
  12. Distinctive:

    If not possible, escalate to executor agent or feature-implement skill

    line 166
  13. Very specific:

    Run pnpm run biome:check and pnpm run astro:check

    line 182

“Common” is measured: kept by at least 6 in 10 of the 7 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Quick Fix

Objective

Fix small bugs, typos, or issues in 1-3 files by following existing code patterns. This skill handles simple, mechanical fixes that don't require architectural decisions. Adapted for this repo: Astro, Svelte, TypeScript; follow AGENTS.md conventions.

Non-Goals

  • Does NOT refactor large sections of code
  • Does NOT add new features
  • Does NOT change architectural patterns
  • Does NOT modify more than 3 files
  • Does NOT handle security-sensitive code

Tier Classification

Tier: 1 - Light/Cheap

Reasoning: Small scope (1-3 files), low risk (follows patterns), mechanical task (no complex reasoning), quick execution.

Inputs

Required Parameters

  • $ISSUE: Description of the bug or issue to fix
  • $FILES: File(s) to examine/modify (optional - will search if not provided)

Optional Parameters

  • $PATTERN: Existing pattern to follow (default: infer from codebase)

Prerequisites

Before running this skill, ensure:

  • Working directory is clean (no uncommitted changes)
  • Issue is clearly defined and small in scope
  • No ongoing work on the same files

Steps

Step 1: Understand the Issue

  • Read the issue description
  • Identify the expected vs actual behavior
  • Locate the relevant file(s)

Step 2: Analyze the Code

  • Read the affected file(s)
  • Understand the existing pattern
  • Identify the root cause

Step 3: Implement the Fix

  • Make the minimal change needed
  • Follow existing code patterns exactly
  • Preserve formatting and style
  • Support dark mode if UI-related (use Tailwind's dark: variant)

Step 4: Validate Changes

Run validation commands for this repo:

pnpm run biome:check
pnpm run astro:check

Output Format

Success Output

## ✅ Quick Fix Complete

### Issue
{Brief description of what was fixed}

### Changes
- `{file1}`: {what changed}
- `{file2}`: {what changed}

### Validation
- Biome: ✅ Clean
- TypeScript: ✅ Passing

### Commit Message
fix: {description}

Failure Output

## ❌ Quick Fix Not Possible

### Reason
{Why this can't be fixed with quick-fix}

### Recommendation
{Escalate to Tier 2 or provide alternative}

Guardrails

Scope Limits

  • Maximum files: 3
  • Maximum LOC: 100
  • Allowed: Any directory in src/
  • Forbidden: Security-sensitive files

Safety Checks

Before making changes:

  • Change is minimal and targeted
  • No architectural modifications
  • Follows existing patterns (see AGENTS.md, docs/STANDARDS.md)
  • No new dependencies added

Stop Conditions

Stop immediately if:

  • Issue requires more than 3 files
  • Change exceeds 100 LOC
  • Requires understanding complex business logic
  • Requires adding new dependencies
  • Existing patterns are unclear

Definition of Done

  • Issue is resolved
  • pnpm run biome:check passes
  • pnpm run astro:check passes
  • Change follows existing patterns
  • Change is minimal (no over-engineering)

Escalation Conditions

Escalate to Tier 2 if:

  • Scope exceeds 3 files
  • Root cause is complex
  • Fix requires new patterns
  • Tests need to be written (testing not configured)

Escalation Path:

  1. Try to break into smaller fixes
  2. If not possible, escalate to executor agent or feature-implement skill

Examples

Example 1: Fix a Typo

Context: Typo in component text

Input:

$ISSUE: Hero section says "Wellcome" instead of "Welcome"
$FILES: src/components/home/HeroSection/HeroSection.astro

Execution:

  1. Open file, find typo, replace
  2. Run pnpm run biome:check and pnpm run astro:check
  3. Commit with fix: correct typo in hero section

Example 2: Fix Dark Mode Issue

Context: Component doesn't support dark mode

Input:

$ISSUE: Footer text is invisible in dark mode
$FILES: src/components/Footer.astro

Execution:

  1. Open file, add dark:text-gray-100 classes
  2. Run pnpm run biome:check
  3. Commit with fix: add dark mode support to footer

Example 3: Escalation

Context: Bug affects multiple components

Input:

$ISSUE: Methodology reader navigation is broken across all sections
$FILES: src/components/pages/MethodologyPage.astro + reader components

Result: Escalate — involves multiple files and complex rendering logic; use Tier 2.

Related

  • doc-edit - Documentation-only fixes
  • type-fix - TypeScript type errors only
  • reviewer - For reviewing fixes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.