Skip to content

BjornMelin/dev-skills / archive/skills/recent-code-bugfix

recent-code-bugfix

Unverified

Find + fix bug current author introduced in last week, cwd. Triggers—proactive recent-change fix, empty prompt, triage recent commits. Root cause = author’s own diffs.

Recent Code Bugfix

Overview

Find a bug introduced by the current author in the last week, implement a fix, and verify it when possible. Operate in the current working directory, assume the code is local, and ensure the root cause is tied directly to the author’s own edits.

Workflow

1) Establish the recent-change scope

Use Git to identify the author and changed files from the last week.

  • Determine the author from git config user.name/user.email. If unavailable, use the current user’s name from the environment or ask once.
  • Use git log --since=1.week --author=<author> to list recent commits and files. Focus on files touched by those commits.
  • If the user’s prompt is empty, proceed directly with this default scope.

2) Find a concrete failure tied to recent changes

Prioritize defects that are directly attributable to the author’s edits.

  • Look for recent failures (tests, lint, runtime errors) if logs or CI outputs are available locally.
  • If no failures are provided, run the smallest relevant verification (single test, file-level lint, or targeted repro) that touches the edited files.
  • Confirm the root cause is directly connected to the author’s changes, not unrelated legacy issues. If only unrelated failures are found, stop and report that no qualifying bug was detected.

3) Implement the fix

Make a minimal fix that aligns with project conventions.

  • Update only the files needed to resolve the issue.
  • Avoid adding extra defensive checks or unrelated refactors.
  • Keep changes consistent with local style and tests.

4) Verify

Attempt verification when possible.

  • Prefer the smallest validation step (targeted test, focused lint, or direct repro command).
  • If verification cannot be run, state what would be run and why it wasn’t executed.

5) Report

Summarize the root cause, the fix, and the verification performed. Make it explicit how the root cause ties to the author’s recent changes.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall