Aakash Dhar Skills

Analyzes code for performance issues including slow algorithms, memory leaks, unnecessary re-renders, database query problems, and resource bottlenecks. Use when the user says "this is slow", "optimize this", "performance issue", "why is this taking so long?", or "make this faster".

Detects code smells, suggests design pattern improvements, and restructures code while preserving existing behavior. Use when the user says "refactor this", "clean up this code", "this code is messy", "improve code quality", "reduce complexity", "simplify this", "make this more maintainable", "code smells", or "this function is too long".

Prepares and creates a pull request by analyzing changes, generating a descriptive title and body, running pre-PR checks, and submitting via GitHub/GitLab CLI. Use when the user says "create a PR", "open a pull request", "submit PR", "prepare PR", "ready for review", or "push and create PR".

Reviews code for bugs, security issues, performance problems, and adherence to best practices. Use when the user asks to "review this code", "check my code", "is this code good?", or before submitting a PR.

Generates a complete local development setup guide by analyzing the project, checking prerequisites, running setup steps, and verifying everything works. Use when the user says "help me set up this project", "how do I run this locally?", "setup guide", "onboard me", "I just cloned this repo", "dev environment setup", or "getting started".

Generates comprehensive tests for a given file, function, class, or module. Covers unit tests, integration tests, edge cases, error paths, and mocking. Use when the user says "write tests", "add tests", "test this", "create tests for", "generate test cases", "cover this with tests", or "improve test coverage".

Generates documentation for code including function/class docstrings, module READMEs, API documentation, inline comments, and architecture overviews. Use when the user says "document this", "add docs", "add comments", "generate README", "what does this code do?", "write API docs", or "this needs documentation".

Analyzes test coverage gaps, identifies untested code paths, prioritizes which tests to write based on risk, and helps improve overall test quality. Use when the user says "what's not tested?", "check test coverage", "what tests are missing?", "improve coverage", or "are my tests good enough?".

Scans code for security vulnerabilities including injection attacks, authentication flaws, exposed secrets, insecure dependencies, and data exposure. Use when the user says "security review", "is this secure?", "check for vulnerabilities", "audit this", or before deploying to production.

Estimates effort for tasks and tickets by analyzing code complexity, dependencies, scope, risk, and historical patterns. Use when the user says "how long will this take?", "estimate this", "how much effort?", "size this ticket", "story points", "can we do this in a sprint?", "level of effort", or "is this a big change?".

Analyzes feature specs, tickets, PRDs, and proposals for hidden complexity, scope creep risks, missing requirements, ambiguous language, unstated assumptions, and unrealistic timelines. Produces a structured scope assessment with flags and recommendations. Saves output to project-decisions/ folder. Use when the user says "scope check", "is this bigger than it sounds?", "check this spec", "review this ticket", "hidden complexity", "scope creep", "what are we missing", "sanity check this", "is this realistic?", "review this PRD", or "what could go wrong with this plan?".

Compares building a solution internally versus buying/adopting a third-party tool, service, or library. Analyzes cost (total cost of ownership), effort, risk, vendor lock-in, maintenance burden, feature fit, and strategic alignment. Produces a structured recommendation. Saves output to project-decisions/ folder. Use when the user says "build vs buy", "build or buy", "should we build this ourselves", "should we use a service for this", "roll our own or use", "make vs buy", "build in-house or", "vendor comparison", "evaluate tools for", or "should we use X or build our own".

Creates and maintains a living project risk register by analyzing the codebase, dependencies, team structure, timeline, and technical decisions. Identifies risks, scores them by likelihood and impact, assigns owners, tracks mitigations, and flags risks that have changed since last assessment. Saves output to project-decisions/ folder. Use when the user says "risk register", "project risks", "what could go wrong", "risk assessment", "identify risks", "update risks", "risk review", "what are our risks", or "flag risks for the project".

Evaluates technical proposals, "should we do X instead of Y?" questions, tool comparisons, and architecture suggestions. Analyzes feasibility, compares options with structured pros/cons, estimates effort and risk, and provides a clear recommendation. Saves output to project-decisions/ folder. Use when the user says "should we", "what if we", "is it worth", "should we switch to", "compare X vs Y", "evaluate this proposal", "tech decision", or brings up a technical suggestion from a team discussion.

Generates a structured penetration testing report based on OWASP standards including OWASP Top 10, ASVS, and WSTG methodology. Scans code for vulnerabilities, maps findings to OWASP categories, assigns CVSS scores, and produces a professional pentest report. Use when the user says "pentest report", "penetration testing", "OWASP audit", "OWASP report", "security assessment", "vulnerability assessment", "application security test", or "OWASP compliance check".

Analyzes how a proposed change affects existing systems, services, teams, APIs, databases, infrastructure, and workflows. Maps blast radius, identifies dependencies, flags breaking changes, and produces a detailed impact report. Saves output to project-decisions/ folder. Use when the user says "what would break if", "impact analysis", "blast radius", "what does this affect", "who is impacted", "dependency check", "what breaks if we change", "ripple effects", or "change impact".

Generates structured incident postmortem reports by analyzing git history, recent deployments, code changes, logs, and error patterns. Produces a blameless postmortem with timeline, root cause analysis, impact assessment, remediation actions, and prevention measures. Saves output to project-decisions/ folder. Use when the user says "incident report", "postmortem", "what went wrong", "outage report", "root cause analysis", "RCA", "write a post-mortem", "incident review", "we had an incident", "production issue", or "site went down".

Quantifies technical debt across the codebase by scanning for code smells, outdated dependencies, complexity hotspots, missing tests, TODOs, dead code, and architectural issues. Produces a prioritized report with effort estimates and business impact. Saves output to project-decisions/ folder. Use when the user says "tech debt report", "how much tech debt", "technical debt", "code health", "codebase health check", "what needs cleanup", "debt audit", "code quality report", "health check", or "what's the state of our codebase?".

Scans project dependencies for known vulnerabilities (CVEs), categorizes them into three severity-based reports (Critical/High, Medium, Low), and generates detailed markdown documents with remediation guidance. Saves output to project-decisions/ folder. Use when the user says "vulnerability report", "dependency vulnerabilities", "CVE report", "package vulnerabilities", "npm audit report", "dependency scan", "vulnerable packages", "security vulnerabilities in dependencies", or "generate vulnerability reports".