Total Skills
2
Author Profile: brockoffdev
Skills published by brockoffdev with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
clean-code
0
Stars
0
Downloads
0
pragmatic-programmer
0
Stars
0
Downloads
0
Published Skills
clean-code
Apply the standards from Robert C. Martin's "Clean Code" when the user asks you to "clean up" code, "apply clean code," review code quality, "make this cleaner/more readable," improve naming, shrink long functions, straighten out comments, or otherwise critique existing code against craftsmanship standards. Also use when the user asks for a code review, asks "what's wrong with this code," complains about readability, or asks to audit a file or module for smells. This skill covers the opinionated line-by-line standards — naming, function size, comments, error handling, tests, classes — that the book codifies. Do not use for greenfield architecture, algorithm design, or requests that are clearly about performance optimization or language-specific idioms.
Repository SourceNeeds Review
pragmatic-programmer
Apply the engineering habits, decision-making posture, and practices from "The Pragmatic Programmer" when the user is asking how to *approach* a programming task, tool, or decision rather than how to write or fix a specific piece of code. Use for questions about engineering judgment and tradeoffs ("should I do X or Y," "how do I decide between A and B"), decoupling and architectural habits, defensive programming posture, debugging *approach* (not just "debug this"), estimation, requirements discovery, prototyping, tool workflows (shell, editor, version control, automation), and project-level practices. Also use when the user seems stuck, is hedging, is "programming by coincidence" without understanding why something works, needs to make a reversible or irreversible decision, or is asking how an experienced engineer would think about a situation. This skill is about engineering habits and judgment, not about line-by-line code critique or mechanical transformation of existing code. Do not use for pure algorithm
Repository SourceNeeds Review