alexei-led/fixing-code
dist/claude/plugins/dev-flow/skills/fixing-code/SKILL.md
Fix code defects with a reproducible feedback loop, root-cause diagnosis, minimal patch, regression test, and clean verification. Use when debugging, diagnosing, or resolving lint/test/build failures. NOT for behavior-preserving refactors (use refactoring-code), test-suite cleanup without a production bug (use improving-tests), or code review findings without fixes (use reviewing-code).
$ install --global
skillsauthnpx skillsauth add alexei-led/claude-code-config fixing-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 3:38 AM12.0s1 file scanned
SKILL.md
- argument-hint:
- [diagnose|investigate] [team]
- context:
- fork
- description:
- Fix code defects with a reproducible feedback loop, root-cause diagnosis,
- name:
- fixing-code
- user-invocable:
- true
Fix and Diagnose Code
Follow the base skill. This Claude overlay only defines tool use and execution details.
Fix the requested defect or failing gate one verified issue at a time. Do not expand to unrelated failures without asking. No guessing.
Arguments
diagnoseorinvestigate: use the hard-bug workflow with hypotheses and probes.team: spawn read-only analysis agents to challenge root cause before editing.
Use TaskCreate and TaskUpdate when the fix has more than two steps:
- Reproduce or run the failing gate.
- Read the failing path.
- Diagnose root cause.
- Patch one issue.
- Verify narrow and broad checks.
- Clean up probes.
Tool order
- Run the smallest known failing command or project gate.
- Use
Read,Grep, andGlobto inspect the exact failing path. - Use
AskUserQuestionif logs, payloads, access, repro steps, environment, or instrumentation approval are missing. - Use
Editfor existing files andWriteonly for new files or complete rewrites. - Run the narrow repro after each patch.
- Run the relevant broader check before final output.
Do not use destructive git commands. Do not use --no-verify.
Repro commands
Prefer configured project commands. Examples:
make lint
make test
go test ./...
ruff check .
pytest --tb=short
bun test
npm test
Use only commands supported by the repo and available tools. Browser-only debugging
belongs in browser-automation unless a cheaper CLI/unit signal exists.
Hard-bug mode
Before editing, write 3-5 ranked falsifiable hypotheses. Probe one at a time. If
you add temporary logs, tag them with [DEBUG-<short-id>] and remove them before
final output.
If claude-mem is available, search for prior gotchas on failing files. Treat memory as a hint, not proof.
If team is set, agents analyze only. Ask for root cause, evidence, suggested fix,
priority, and confidence. Verify their claims before editing.
Scope control
- If all checks pass and no bug is reproduced, report that and ask for a repro artifact.
- If the failing gate contains unrelated failures, fix the requested issue first and ask before expanding.
- If the only test seam is too shallow, say so; do not create fake-confidence tests.
- If a patch causes new failures, diagnose that failure before continuing.
Output
Use FIX COMPLETE for applied fixes:
FIX COMPLETE
============
Mode: standard | diagnose | team | diagnose+team
Issues found: X
Fixed: Y
Remaining: Z
Status: CLEAN | NEEDS ATTENTION
Root cause:
- <verified cause and evidence>
Changes:
- file:line — fix
Verification:
- <command> — pass/fail/skipped with reason
Use BLOCKED or Proposed Changes when tools, access, permission, or user input
prevents applying the fix. Include the exact missing artifact or permission needed.
Do not claim clean without a passing check or explicit skipped-check reason.
Related Skills
alexei-led/writing-shell
tools
VerifiedTrustedCommunity
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, TypeScript, Go, web code, or infrastructure operations.
33SKILL.mdUpdated Jun 5, 2026
alexei-led/spec-flow
tools
VerifiedTrustedCommunity
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview.
33SKILL.mdUpdated Jun 5, 2026
alexei-led/operating-infra
testing
VerifiedTrustedCommunity
Author, inspect, troubleshoot, and review infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances, or service health. NOT for deploy/apply/rollback workflows (see deploying-infra). NOT for shell scripts or generic command pipelines (see writing-shell).
33SKILL.mdUpdated Jun 5, 2026
alexei-led/configuring-git-hygiene
development
VerifiedTrustedCommunity
Configure safe git workflow hygiene: pre-commit/pre-push hooks, Gitleaks secret scanning, .gitignore rules, local git config, and guardrails. Use when setting up git hooks, gitleaks/git leaks, staged pre-commit checks, pre-push validation, core.hooksPath, .gitignore, or git config best practices. NOT for creating commits (use committing-code), cleaning branches/worktrees (use cleanup-git), or creating worktrees (use using-git-worktrees).
33SKILL.mdUpdated Jun 5, 2026