Bug Fix Knowledge logo

Bug Fix Knowledge

Community
dykyi-roman
bug-fix-knowledge

Bug fix knowledge base. Provides bug categories, symptoms, fix patterns, and minimal intervention principles for PHP 8.4 projects.

Overview

Publisherdykyi-roman
Repositoryawesome-claude-code
Skill namebug-fix-knowledge
Stars
98
Forks
25
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dykyi-roman on GitHub. Read the source before you install it.

Installation

Install the Bug Fix Knowledge AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-code.git /tmp/awesome-claude-code
mkdir -p .claude/skills
cp -r /tmp/awesome-claude-code/skills/bug-fix-knowledge .claude/skills/bug-fix-knowledge
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bug Fix Knowledge in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bug Fix Knowledge on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bug Fix Knowledge is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Bug Fix Knowledge Base

Comprehensive knowledge for diagnosing and fixing bugs in PHP applications following DDD, CQRS, and Clean Architecture patterns.

Bug Categories and Symptoms

1. Logic Errors

Symptoms:

  • Incorrect output for valid input
  • Wrong branch taken in conditionals
  • Inverted boolean logic
  • Off-by-one errors in loops
  • Missing edge case handling

Common Causes:

  • > instead of >=, && instead of ||
  • Negation errors (!$condition vs $condition)
  • Loop boundary mistakes (< count vs <= count)
  • Missing break in switch statements

Fix Pattern:

php
// Before: Logic error
if ($amount > $limit) { // Should be >=
    throw new LimitExceededException();
}

// After: Fixed
if ($amount >= $limit) {
    throw new LimitExceededException();
}

2. Null Pointer Issues

Symptoms:

  • "Call to a member function on null"
  • "Cannot access property on null"
  • Unexpected null returns
  • Missing null checks after optional operations

Common Causes:

  • Repository returning null for non-existent entity
  • Optional relationships not checked
  • Nullable parameters not validated
  • Method chaining on potentially null objects

Fix Pattern:

php
// Before: Null pointer risk
$user = $this->userRepository->find($id);
$email = $user->getEmail(); // Crashes if user is null

// After: Safe with null check
$user = $this->userRepository->find($id);
if ($user === null) {
    throw new UserNotFoundException($id);
}
$email = $user->getEmail();

// Alternative: Null coalescing
$email = $user?->getEmail() ?? throw new UserNotFoundException($id);

3. Boundary Issues

Symptoms:

  • Array index out of bounds
  • Empty collection access
  • String index errors
  • Numeric overflow/underflow

Common Causes:

  • Accessing first/last element without checking emptiness
  • Loop index exceeding array size
  • Integer overflow in calculations
  • Missing bounds validation

Fix Pattern:

php
// Before: Boundary issue
$firstItem = $items[0]; // Crashes if empty

// After: Safe boundary check
if ($items === []) {
    throw new EmptyCollectionException('items');
}
$firstItem = $items[0];

// Alternative: Using first() with default
$firstItem = $items[0] ?? throw new EmptyCollectionException('items');

4. Race Conditions

Symptoms:

  • Intermittent failures
  • Data corruption under load
  • Lost updates
  • Duplicate records

Common Causes:

  • Check-then-act without locking
  • Shared mutable state
  • Missing database transactions
  • Concurrent file access

Fix Pattern:

php
// Before: Race condition
if (!$this->repository->exists($id)) {
    $this->repository->save($entity); // Another process might insert between check and save
}

// After: Atomic operation with locking
$this->lockManager->acquire("entity:$id");
try {
    if (!$this->repository->exists($id)) {
        $this->repository->save($entity);
    }
} finally {
    $this->lockManager->release("entity:$id");
}

// Alternative: Database-level uniqueness
// Use UNIQUE constraint + INSERT ... ON DUPLICATE KEY

5. Resource Leaks

Symptoms:

  • Memory exhaustion over time
  • "Too many open files"
  • Database connection pool exhaustion
  • Slow performance degradation

Common Causes:

  • Unclosed file handles
  • Missing database connection release
  • Event listeners not removed
  • Circular references preventing GC

Fix Pattern:

php
// Before: Resource leak
$handle = fopen($path, 'r');
$content = fread($handle, filesize($path));
// Missing fclose()

// After: Proper resource management
$handle = fopen($path, 'r');
try {
    $content = fread($handle, filesize($path));
} finally {
    fclose($handle);
}

// Better: Use high-level functions
$content = file_get_contents($path);

6. Exception Handling Issues

Symptoms:

  • Silent failures
  • Generic error messages
  • Lost exception context
  • Swallowed exceptions

Common Causes:

  • Empty catch blocks
  • Catching too broad exception types
  • Not re-throwing after logging
  • Missing exception chaining

Fix Pattern:

php
// Before: Swallowed exception
try {
    $this->service->process($data);
} catch (Exception $e) {
    // Silent failure - bug hidden
}

// After: Proper exception handling
try {
    $this->service->process($data);
} catch (ValidationException $e) {
    throw new ProcessingFailedException(
        "Failed to process data: {$e->getMessage()}",
        previous: $e
    );
}

7. Type Issues

Symptoms:

  • "Type error: Argument must be of type X, Y given"
  • Unexpected type coercion
  • String/int confusion
  • Array/object mismatch

Common Causes:

  • Missing strict_types declaration
  • Implicit type casting
  • Mixed types from external sources
  • Legacy code without type hints

Fix Pattern:

php
// Before: Type issue
function calculate($amount) { // No type hint
    return $amount * 1.1; // Fails if string passed
}

// After: Strict typing
declare(strict_types=1);

function calculate(float $amount): float {
    return $amount * 1.1;
}

8. SQL Injection

Symptoms:

  • Security vulnerabilities
  • Unexpected query results
  • Data corruption
  • Authentication bypass

Common Causes:

  • String concatenation in queries
  • Missing parameter binding
  • Unvalidated user input in queries
  • Dynamic table/column names

Fix Pattern:

php
// Before: SQL injection vulnerability
$query = "SELECT * FROM users WHERE email = '$email'";

// After: Parameterized query
$query = "SELECT * FROM users WHERE email = :email";
$stmt = $pdo->prepare($query);
$stmt->execute(['email' => $email]);

9. Infinite Loops

Symptoms:

  • Application hangs
  • 100% CPU usage
  • Request timeouts
  • Memory exhaustion

Common Causes:

  • Missing or unreachable exit condition
  • Iterator not advancing
  • Recursive call without base case
  • Circular dependencies in processing

Fix Pattern:

php
// Before: Potential infinite loop
while ($item = $queue->pop()) {
    $this->process($item);
    // If process() adds items back to queue, infinite loop
}

// After: Safe with limit
$maxIterations = 10000;
$iterations = 0;
while ($item = $queue->pop()) {
    if (++$iterations > $maxIterations) {
        throw new MaxIterationsExceededException($maxIterations);
    }
    $this->process($item);
}

Minimal Intervention Principles

1. Single Responsibility Fix

  • Fix ONLY the bug, nothing else
  • No refactoring while fixing
  • No "while I'm here" improvements
  • Keep the diff minimal

2. Preserve Behavior

  • Existing tests must pass
  • API contracts must not change
  • Side effects must be preserved (if intentional)
  • Error messages format should match

3. Backward Compatibility

  • Public method signatures unchanged
  • Return types unchanged
  • Exception types unchanged
  • Event payloads unchanged

4. Test First

  • Write failing test that reproduces bug
  • Fix should make test pass
  • No fix without reproduction test

Fix Validation Checklist

Before applying a fix, verify:

  1. Reproduction Test Exists

    • Test fails without fix
    • Test passes with fix
    • Test covers edge cases
  2. Minimal Change

    • Only affected code changed
    • No unrelated refactoring
    • No formatting changes
  3. No Regressions

    • All existing tests pass
    • No new warnings
    • Performance not degraded
  4. Code Quality

    • No new code smells
    • SOLID principles respected
    • DDD patterns maintained
  5. Documentation

    • PHPDoc updated if needed
    • CHANGELOG entry added
    • Issue linked in commit

DDD-Specific Bug Patterns

Domain Layer Bugs

  • Value Object validation bypass
  • Entity invariant violation
  • Aggregate boundary crossing
  • Domain Event lost

Application Layer Bugs

  • Use Case not transactional
  • Command/Query mixing
  • Missing authorization check
  • Event handler not idempotent

Infrastructure Layer Bugs

  • Repository returning detached entity
  • Cache invalidation missing
  • Message not acknowledged
  • Connection not released

Quick Reference: Fix by Error Message

Error MessageLikely BugQuick Fix
"Call to member function on null"Null pointerAdd null check
"Undefined array key"Boundary issueCheck array_key_exists
"Type error: Argument X"Type issueAdd type validation
"Maximum execution time"Infinite loopAdd iteration limit
"Allowed memory exhausted"Resource leakClose resources in finally
"Integrity constraint violation"Race conditionAdd locking/transaction
"Cannot modify readonly property"Immutability violationCreate new instance

Frequently asked questions

What does the Bug Fix Knowledge AI skill do?

Bug fix knowledge base. Provides bug categories, symptoms, fix patterns, and minimal intervention principles for PHP 8.4 projects.

Why use Bug Fix Knowledge on TypingMind?

Because you install it once and use it with any model. Bug Fix Knowledge is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bug Fix Knowledge in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dykyi-roman/awesome-claude-code/tree/master/skills/bug-fix-knowledge. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Bug Fix Knowledge?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bug Fix Knowledge?

As many as you like. As long as a model supports skills, you can use Bug Fix Knowledge with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bug Fix Knowledge AI skill free?

Yes. It is published on GitHub by dykyi-roman under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇