Agent skill

Thoroughness

by pr-pm in pr-pm/prpm

A skill your agent uses when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without…

MITAuto-check passedTesting & QA

Install Thoroughness

skills CLI
$ npx skills add pr-pm/prpm --skill thoroughness -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pr-pm/prpm thoroughness --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/thoroughness .claude/skills/thoroughness && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
thoroughness
GitHub stars
122
Token cost
~1.1k tokens
SKILL.md length
445 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without…

  • Works in 3 steps: Comprehensive Analysis (20% of time) → Systematic Implementation (60% of time) → Comprehensive Verification (20% of time)
  • Implementing complex multi-step tasks
  • SKILL.md covers Purpose, When to Use, Methodology and Anti-Patterns to Avoid, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Thoroughness is an agent skill from pr-pm/prpm. Use when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without shortcuts through systematic analysis, implementation, and verification phases

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. The repository describes itself as: The universal registry for AI coding tools. The licence is MIT.

When your agent uses it

  • Implementing complex multi-step tasks
  • Fixing critical bugs
  • Quality and completeness matter more than speed - ensures comprehensive implementation without shortcuts through systematic analysis
  • Verification phases

Example prompts

  • “/thoroughness”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Comprehensive Analysis (20% of time)
  2. Systematic Implementation (60% of time)
  3. Comprehensive Verification (20% of time)

What it can do on your machine

Read from SKILL.md and the folder at commit 5f993e6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Thoroughness loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 445 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pr-pm/prpm at commit 5f993e6, republished under its MIT licence (© pr-pm). 445 words, ~1,097 tokens.

Download SKILL.mdSave it as .claude/skills/thoroughness/SKILL.md (or your agent's skills folder).
name
thoroughness
description
Use when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without shortcuts through systematic analysis, implementation, and verification phases

Thoroughness

Purpose

This skill ensures comprehensive, complete implementation of complex tasks without shortcuts. Use this when quality and completeness matter more than speed.

When to Use

  • Fixing critical bugs or compilation errors
  • Implementing complex multi-step features
  • Debugging test failures
  • Refactoring large codebases
  • Production deployments
  • Any task where shortcuts could cause future problems

Methodology

Phase 1: Comprehensive Analysis (20% of time)
  1. Identify All Issues

    • List every error, warning, and failing test
    • Group related issues together
    • Prioritize by dependency order
    • Create issue hierarchy (what blocks what)
  2. Root Cause Analysis

    • Don't fix symptoms, find root causes
    • Trace errors to their source
    • Identify patterns in failures
    • Document assumptions that were wrong
  3. Create Detailed Plan

    • Break down into atomic steps
    • Estimate time for each step
    • Identify dependencies between steps
    • Plan verification for each step
    • Schedule breaks/checkpoints
Phase 2: Systematic Implementation (60% of time)
  1. Fix Issues in Dependency Order

    • Start with foundational issues
    • Fix one thing completely before moving on
    • Test after each fix
    • Document what was changed and why
  2. Verify Each Fix

    • Write/run tests for the specific fix
    • Check for side effects
    • Verify related functionality still works
    • Document test results
  3. Track Progress

    • Mark issues as completed
    • Update plan with new discoveries
    • Adjust time estimates
    • Note any blockers immediately
Phase 3: Comprehensive Verification (20% of time)
  1. Run All Tests

    • Unit tests
    • Integration tests
    • E2E tests
    • Manual verification
  2. Cross-Check Everything

    • Review all changed files
    • Verify compilation succeeds
    • Check for console errors/warnings
    • Test edge cases
  3. Documentation

    • Update relevant docs
    • Add inline comments for complex fixes
    • Document known limitations
    • Create issues for future work
Show full SKILL.md (181 more words)Show less

Anti-Patterns to Avoid

  • ❌ Fixing multiple unrelated issues at once
  • ❌ Moving on before verifying a fix works
  • ❌ Assuming similar errors have the same cause
  • ❌ Skipping test writing "to save time"
  • ❌ Copy-pasting solutions without understanding
  • ❌ Ignoring warnings "because it compiles"
  • ❌ Making changes without reading existing code first

Quality Checkpoints

  • Can I explain why this fix works?
  • Have I tested this specific change?
  • Are there any side effects?
  • Is this the root cause or a symptom?
  • Will this prevent similar issues in the future?
  • Is the code readable and maintainable?
  • Have I documented non-obvious decisions?

Example Workflow

Bad Approach (Shortcut-Driven)
1. See 24 TypeScript errors
2. Add @ts-ignore to all of them
3. Hope tests pass
4. Move on
Good Approach (Thoroughness-Driven)
1. List all 24 errors systematically
2. Group by error type (7 missing types, 10 unknown casts, 7 property access)
3. Find root causes:
   - Missing @types/tar package
   - No type assertions on fetch responses
   - Implicit any types in callbacks
4. Fix by category:
   - Install @types/tar (fixes 7 errors)
   - Add proper type assertions to registry-client.ts (fixes 10 errors)
   - Add explicit parameter types (fixes 7 errors)
5. Test after each category
6. Run full test suite
7. Document what was learned

Time Investment

  • Initial: 2-3x slower than shortcuts
  • Long-term: 10x faster (no debugging later, no rework)
  • Quality: Near-perfect first time
  • Maintenance: Minimal

Success Metrics

  • ✅ 100% of tests passing
  • ✅ Zero warnings in production build
  • ✅ All code has test coverage
  • ✅ Documentation is complete and accurate
  • ✅ No known issues or TODOs left behind
  • ✅ Future developers can understand the code

Mantras

  • "Slow is smooth, smooth is fast"
  • "Do it right the first time"
  • "Test everything, assume nothing"
  • "Document for your future self"
  • "Root causes, not symptoms"

© pr-pm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/thoroughness of pr-pm/prpm.

Open the folder on GitHubat commit 5f993e6

Compare with similar skills

Thoroughness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Thoroughness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Thoroughness this skillpr-pm/prpm122—~1.1kAutomated safety check: PassMIT
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Clawteam DevHKUDS/ClawTeam5.5k1 repos~1.1kAutomated safety check: PassMIT
Browser Testing with Chrome DevToolsaddyosmani/agent-skills102k4 repos~3.5kAutomated safety check: WarnMIT
Apple Container Test RunnerRustPython/RustPython22k—~467Automated safety check: PassMIT

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • Clawteam Dev

    HKUDS/ClawTeam

    A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…

    5.5k GitHub starsUsed in 1 repo~1.1k tokens
    Testing & QAAuto-check passed
  • Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.

    102k GitHub starsUsed in 4 repos~3.5k tokens
    Testing & QAAuto-check: warnings
  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed
  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

More from pr-pm/prpm

All 35 skills in this repo
  • Reference for writing Claude Code agent files: location, frontmatter fields, validation limits, tool and model choices, and the required content format.

    122 GitHub starsUsed in 3 repos~4k tokens
    Auto-check passed
  • Covers how to build, configure and publish Claude Code hooks: event types, exit codes, JSON I/O, and PRPM packaging.

    122 GitHub starsUsed in 2 repos~3.9k tokens
    Auto-check: notes
  • Shows how to write .claude/rules/ files correctly: paths frontmatter instead of globs, quoted glob patterns, global rules and conversion of Cursor rules.

    122 GitHub starsUsed in 2 repos~551 tokens
    Auto-check passed
  • Reference for writing portable Agent Skills packages, covering SKILL.md frontmatter limits, name rules, directory layout and where Codex CLI, GitHub Copilot and Amp look for skills.

    122 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • A skill your agent uses when building custom Kiro AI agents or when user asks for agent configurations - provides JSON structure, tool configuration, prompt patterns, and security best practices for…

    122 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • A skill your agent uses when creating OpenCode agents - provides markdown format with YAML frontmatter, mode/tools/permission configuration, and best practices for specialized AI assistants

    122 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

Questions about Thoroughness

What does Thoroughness do?

A skill your agent uses when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without…. Thoroughness is an agent skill from pr-pm/prpm.

When should I use Thoroughness?

Thoroughness fits situations like: implementing complex multi-step tasks; fixing critical bugs; quality and completeness matter more than speed - ensures comprehensive implementation without shortcuts through systematic analysis; verification phases.

How do I install Thoroughness in Claude Code?

Run `npx skills add pr-pm/prpm --skill thoroughness -a claude-code`. Or copy the skill folder (.claude/skills/thoroughness in pr-pm/prpm) into .claude/skills/thoroughness in your project. Claude Code loads it when a task matches its description.

How do I install Thoroughness in Codex?

Run `npx skills add pr-pm/prpm --skill thoroughness -a codex`. Or copy the skill folder (.claude/skills/thoroughness in pr-pm/prpm) into .agents/skills/thoroughness in your project. Codex loads it when a task matches its description.

Can I use Thoroughness in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pr-pm/prpm --skill thoroughness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/thoroughness, .gemini/skills/thoroughness, .github/skills/thoroughness and .opencode/skills/thoroughness in your project.

What does Thoroughness need to run?

SKILL.md names no scripts, command-line tools or credentials: Thoroughness is instructions for the agent only.

Does Thoroughness access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Thoroughness safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Thoroughness use?

Thoroughness is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Thoroughness use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Thoroughness?

Skills that share tags, products or a category with Thoroughness: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Rust TDD Workflow (rtk-ai/rtk, 83k stars), Clawteam Dev (HKUDS/ClawTeam, 5.5k stars) and Browser Testing with Chrome DevTools (addyosmani/agent-skills, 102k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Thoroughness?

pr-pm (a GitHub organization) maintains it in pr-pm/prpm, which has 122 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 6, 2026.

Source: pr-pm/prpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.