Hyhmrright Agent Skills
9 skills published by hyhmrright across 1 repository. Together they weigh 17 622 tokens — that is what loading all of them at once would cost you in context.
9 skills 17 622 tokens total
> Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". or "give me a codebase tour" (use onboarding mode). questions — this skill analyzes structural/module-level concerns, not individual functions.
> Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.
> Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and audit", "do the X part again". (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.
> Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).
> PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. questions, or framework/tool questions where no existing code is shared.
> architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. issues", "clean up the whole project", or asks for a single command that both diagnoses and remediates quality problems. findings without code changes; single-dimension reviews (use the focused skill checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime.
> Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an poor readability. take forever", "tests pass but bugs still reach production", or "we have too many mocks". workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
> Scaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". an existing skill, or authoring skills for some other plugin.
> all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.