harshitsinghbhandari
15 verified skills
code-quality-audit
Comprehensive code quality audit that combines ruthless analysis with a solution-focused refactoring roadmap. Reads source code files, produces a brutal audit report with per-file quality scores, and generates prioritized refactoring improvements.
development
edge-case-hunter
Exhaustive edge-case review that traces branching paths and boundary conditions in a diff or code sample and reports only unhandled cases. Use when the user asks to hunt edge cases, boundary conditions, missing guards, or wants an edge-case-focused review.
development
architecture-audit
Comprehensive architecture audit that combines ruthless analysis with solution-focused improvement planning. Reads architecture Markdown files, produces a brutal audit report with file/component scores, and generates a prioritized improvements roadmap.
testing
code-refactor-executor
Executes a multi-stage refactoring plan based on existing `audit.md` and `improvements.md` files. Reads the recommendations, scans the target source code, and builds an implementation roadmap before applying atomic code transformations.
development
itemized-functions
Generate exhaustive integration functions with comprehensive test suites for all 3rd-party APIs and external services. Automatically creates function wrappers, individual test files, integrated test runners, and a detailed report of API behavior, response signatures, latency, and failure modes.
development
llm-council
Convene an LLM Council for high-stakes decisions requiring multiple perspectives. Use when the user says "council this", "run the council", "get council input", or asks for multi-perspective analysis on strategic decisions like pricing, positioning, pivots, hiring, or any question where being wrong is expensive. Do NOT use for simple factual questions, writing tasks, or summarization.
testing
llm-forge
Run existing work through 5 specialist craftspeople who each produce an improved version, then peer-review and synthesize the best into a single improved artifact. Use when the user says "forge this", "improve this", "make this better", "level this up", "refine this", or asks for multi-angle improvement on code, copy, strategy, plans, designs, or any artifact where the current version works but could be significantly better. Do NOT use for decisions (use llm-council), simple edits, or creation from scratch.
development
pr-learning
Extract actionable learnings from merged PRs by comparing initial submission vs final merged state. Analyzes review cycles to capture what changed and why. Use when the user says "learn from PR", "extract PR learnings", "what did we learn from this PR", or wants to build a knowledge base from merged PRs.
development
resume-critic
Constructively critique resumes from multiple professional perspectives, but only against a specific job description or at least a concrete job title. Use when the user asks for resume review, ATS feedback, interview readiness, bullet improvement, or tailored resume critique for a target job. Do NOT use for full resume rewriting unless the user explicitly asks for rewrites.
testing
resume-rewrite
Rewrite a resume using only the candidate's existing material, but only after a `resume-critic` review has been completed for a specific job description or job title. Use when the user wants the resume rewritten, tightened, or retargeted without inventing new experiences.
testing
resume-upgrade
Propose how to upgrade a resume by identifying missing projects, skills, evidence, and experience-building moves, but only after a `resume-critic` review has been completed for a specific job description or job title. Use when the user wants strategic suggestions beyond the current resume.
development
test-coverage-audit
Comprehensive test suite audit that combines ruthless analysis with a solution-focused roadmap. Reads test suites (unit, integration, e2e) and source code, produces a brutal audit report of test quality and gaps, and generates prioritized testing improvements.
development
update-changelog
Expert skill for maintaining a Keep a Changelog formatted CHANGELOG.md file. Use this skill whenever you add features, fix bugs, or release a new version. You MUST use this skill to record any changes that have a user-facing impact. It handles categorization (Added, Changed, Fixed, etc.), semantic versioning, and reverse-chronological ordering with surgical precision.
development
pr-review
Comprehensive PR review focusing on code quality, test coverage, security, backward compatibility, and what CI cannot check. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
development
boundary-bug-hunter
Aggressive user-flow and boundary-bug analysis on a diff or branch. Auto-detects entry points, traces flows through changed code, finds every seam (cross-module calls, serialization, file I/O, shared state, schema versioning, network/IPC), and refuses to mark the work complete until each unverified boundary has a real round-trip test or an explicit written out-of-scope record persisted in an audit file. Use whenever the user says "boundary check", "seam check", "round-trip check", "flow boundaries", "user-flow check", "before merge", "is this safe to ship", "pre-merge gate", "boundary bugs", "verify the joins", or asks to validate cross-module joins, producer/consumer contracts, or end-to-end coverage of a change. Also use as a final gate from pr-review on any diff that touches more than one file, module, or process. Be pushy. Most surviving production bugs live at seams, not inside units — if the diff crosses any boundary, this skill almost certainly applies.
development