Install
npx skills add milad-ahmd/agent-skills --skill test-gap-hunter
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add milad-ahmd/agent-skills
/plugin install all-skills@milad-agent-skills
This skill is part of the plugin “all-skills”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the test-gap-hunter skill do?
Description from the SKILL.md in the source repository.
Questions about test-gap-hunter
What does the test-gap-hunter skill do?
Finds the riskiest untested code in a project and writes meaningful tests for it using the project's existing test framework and conventions. Use when the user asks to improve coverage, add tests, find untested code, or harden a module before a refactor.
How do I install test-gap-hunter?
In a terminal: npx skills add milad-ahmd/agent-skills --skill test-gap-hunter. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use test-gap-hunter?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is test-gap-hunter safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from milad-ahmd/agent-skills
Grills the user about a planned feature or code change before any code is written. It reads the relevant code and docs first so every question is specific to the repo, asks one decision at a time with a recommended answer, works through scope, behaviour, edge cases, data, failure modes and rollout, then writes a SPEC.md with numbered requirements, Given/When/Then acceptance criteria tied to them and a test plan, checked by a linter that flags vague words and untraced requirements. Use when the user asks to grill or interview them about a feature, pressure-test an implementation plan, write a spec or PRD for a change, or turn a rough feature request into testable requirements before coding.
Researches and writes SEO-optimized, genuinely helpful blog articles, covering keyword and search-intent analysis, competitor outline gaps, title and meta description, headings, FAQ, internal links, and schema, in the brand's voice and following Google's helpful-content and E-E-A-T principles. Use when the user asks to write a blog post or article, do SEO content, or rank for a keyword.
Converts a screenshot, mockup, or Figma export into a production-ready UI component that reuses the project's existing design system (React/Next, Vue, Svelte, React Native, Flutter, or SwiftUI with Tailwind, CSS modules, or a component library), so the result is responsive and accessible. Use when the user shares an image of a UI and asks to build, implement, or recreate it in code.
Roasts a GitHub profile with humor, then gives genuinely useful advice. It analyzes public repos, stars, languages, missing descriptions and licenses, abandoned projects, lazy commit messages, and activity with a data script, and produces a shareable scorecard and a glow-up plan. Use when the user asks to roast, rate, review, or improve a GitHub profile, or asks "what does my GitHub say about me".
Rewrites a repository's README into a polished, star-worthy page with badges, a hero tagline, demo section, quickstart, features, usage, and contributing info. Use when the user asks to improve, rewrite, polish, or "glow up" a README, or when a repo has a missing or weak README.
Scans an AI agent's instruction and tool-config files (CLAUDE.md, AGENTS.md, skills, slash commands, subagents, Cursor and Cline rules, hooks, MCP server configs) for prompt injection, hidden Unicode or HTML-comment instructions, exfiltration commands, and risky permissions or unpinned MCP packages, then recommends what to remove or quarantine. Use when the user installs third-party skills or plugins, clones an unfamiliar repo, adds an MCP server, or asks whether their agent setup is safe to trust.
Reviews a pull request or local branch diff like a senior engineer, covering correctness, security, performance, naming, and missing tests, and produces prioritized, actionable comments (optionally posted to GitHub). Use when the user asks to review a PR, a diff, a branch, or "check my changes before I push".
Brutally honest but constructive critique of a landing page's copy, UX, design, and conversion. Gives a scored roast plus a prioritized fix list and rewritten headline and CTA options, working from a URL, screenshot, or the page's source code. Use when the user asks to roast, review, critique, or improve the conversion of a landing page, homepage, or pricing page.
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.