skills.rest
vlad-ryzhkov
vlad-ryzhkovCOMMUNITY
Explore all skills by this author →
GitHub

auditor

Audits code changes in pull requests for user-facing quality, test coverage, and documentation.

25|14|Updated Feb 1, 2026
Search Tags:#qa#auditing#quality-gate#code-review#acceptance-criteria#end-user
One-click install
npx skills add https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19 --skill auditor-vlad-ryzhkov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auditor
Source: https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19/tree/main/.agents/skills/auditor
Command: npx skills add https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19 --skill auditor-vlad-ryzhkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-user perspective is critical for ensuring that changes meet real-world usability and acceptance criteria before merging. The Auditor acts as the final guard, validating user impact and alignment with project goals.

Core Features & Use Cases

  • End-user oriented review: verifies that changes align with end-user expectations and scenarios.
  • Coverage gap detection: identifies missing tests, unaddressed acceptance criteria, or documentation gaps.
  • Gatekeeper for merges: approves or flags PRs before integration to maintain quality and reliability.

Quick Start

Review AGENTS.md to understand the project philosophy and apply auditor criteria during PR review.

Frequently Asked Questions about auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate acceptance criteria during a pull request review?▼

To validate acceptance criteria during a pull request review, audit code changes against end-user expectations and project guidelines. This verifies user-facing behavior, test coverage, and documentation gaps before approving the merge.

What is an end-user quality gatekeeper for code review?▼

An end-user quality gatekeeper for code review audits code changes to ensure real-world usability and acceptance criteria are met before merging. It acts as a final guard to validate user impact, test coverage, and alignment with project goals.

How do I detect missing test coverage and documentation gaps in a PR?▼

You can detect missing test coverage and documentation gaps in a PR by auditing code changes to identify unaddressed acceptance criteria. This coverage gap detection flags missing tests and edge-case handling to maintain reliability before integration.

Do I need an AGENTS.md file to enforce project guidelines during PR audits?▼

Yes, you need an AGENTS.md file to enforce project guidelines during PR audits. The auditor integrates with project philosophy via AGENTS.md to understand and apply specific end-user quality criteria during the pull request review process.

When should I audit edge-case handling before approving a merge?▼

You should audit edge-case handling before approving a merge whenever user-facing behavior changes are introduced. This ensures the code changes meet real-world usability and acceptance criteria, flagging any gaps in test coverage or documentation prior to integration.

Related Skills

Explore More Software Engineering Skills→
Archive228Archive228
746

sprint-contract

Define sprint objectives and acceptance criteria before coding begins.

Community
Intermediate
daominahdaominah

reviewing-code-and-pr

Review code changes and pull requests for business fit, quality, and security.

Community
Intermediate
nikblanchetnikblanchet

development-standards

Enforce development standards across code, documentation, commits, and pull requests.

Community
Basic
hanzlahabibhanzlahabib
2

rcode-fatima-qa

Generate tests and QA artifacts for implemented features.

Community
Advanced