software-debugging
Find and fix bugs systematically. Use when encountering errors, test failures, or unexpected behavior. Hypothesis-driven debugging to locate root causes and implement minimal fixes.
Browse published AI skills maintained by bryonjacob. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
36Repository stars across indexed skills
0Repository forks
36Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Find and fix bugs systematically. Use when encountering errors, test failures, or unexpected behavior. Hypothesis-driven debugging to locate root causes and implement minimal fixes.
Five-level maturity progression - assessment criteria, upgrade paths, YAGNI enforcement
Analyze test suites for speed bottlenecks, redundancy, and DRY violations. Use when tests are slow, duplicated, or need refactoring.
Level 4 patterns - multi-language orchestration, root + subproject structure
Use when setting up GitHub Actions CI/CD for pull request checks - provides workflow templates for Python, JavaScript, and polyglot projects that run quality gates on every PR
Use when creating static websites with Next.js static export - covers YAML-based content, image optimization, form handling, SEO, and deployment to GitHub Pages/Netlify/Vercel
Learn project conventions, detect patterns, suggest consistency improvements
Level 1 patterns - test-watch, integration-test, complexity, loc, duplicates, slowtests
Perform exploratory QA testing on web applications using Playwright. Navigate flows, analyze pages, find issues, and generate actionable reports with evidence.
Systematic refactoring workflow - use coverage/complexity tools to identify targets, plan issues, execute with tests
Use when building web UIs with Next.js 15+ and React 19 - covers Server Components, App Router, testing with Vitest and Playwright, and accessibility standards
Design, discover, and refactor multi-command workflows for Claude Code
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.