skills.rest
Toqsick
ToqsickCOMMUNITY
Explore all skills by this author →
GitHub

verify-before-fix

Verify bug fix locations against current repository state and git history.

Updated Jul 3, 2026
Search Tags:#git#code review#issue tracking#bug verification#developer efficiency
One-click install
npx skills add https://github.com/Toqsick/MaxClaw --skill verify-before-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-before-fix
Source: https://github.com/Toqsick/MaxClaw/tree/main/.claude/skills/verify-before-fix
Command: npx skills add https://github.com/Toqsick/MaxClaw --skill verify-before-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the verification of bug fixes listed in issue descriptions, preventing time-wasting fixes on stale data, incorrect paths, and already-resolved bugs.

Core Features & Use Cases

  • Bug Verification: Confirm the accuracy of reported bug locations before applying fixes.
  • Repo Layout Mapping: Adjusts reported issue paths to the actual repository layout.
  • Partial Fix Detection: Identifies and accounts for bugs that have already been partially fixed on the current branch.
  • Use Case: For software developers working on bug fixes, it reduces the risk of reintroducing old bugs and improves overall efficiency in bug resolution.

Quick Start

Run the 'verify-before-fix' skill to verify the bug fixes listed in Issue #123.

Frequently Asked Questions about verify-before-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify bug fix locations in a git repository before applying changes?▼

Verifying bug fix locations requires mapping reported issue paths to the actual repository layout and checking historical git changes. This process prevents applying fixes to stale data or incorrect file paths.

Why should I verify issue descriptions before fixing reported bugs?▼

Verifying issue descriptions minimizes unnecessary bug fixes by identifying already-resolved bugs and partial fixes on the current branch. This ensures developers only address actual outstanding issues.

Can I check for partial bug fixes already applied on my current git branch?▼

Checking for partial bug fixes involves analyzing the current repository state against the issue description. It identifies and accounts for code changes already applied to the branch.

How do I map file paths from an issue report to my actual codebase layout?▼

Mapping file paths to the codebase layout involves analyzing the repository structure and adjusting reported issue paths. This ensures the reported line numbers match the actual file locations before applying fixes.

Does this bug verification process work with existing git history and codebases?▼

The bug verification process works by analyzing historical git changes and the current codebase state. It is compatible with standard git workflows and existing repository structures.

What is the best way to avoid reintroducing old bugs during code review?▼

The best way to avoid reintroducing old bugs is to automate bug verification before applying fixes, ensuring the reported issue paths and line numbers match the current repository state.

Related Skills

Explore More Software Engineering Skills→
getsentrygetsentry
246

sentry-code-review

Parse Sentry comments in GitHub PRs and generate targeted fixes.

Official
Advanced
686f6c61686f6c61
105

changelog

Generate changelog entries in Keep a Changelog format from Git history.

Community
Basic
asanexampleasanexample
1

maintaining-docs

Track code modifications and automate repository documentation updates with grep scripting.

Official
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic