dev-audit

Generate architecture, security, and compatibility findings for GitHub pull request audits.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-audit
Source: https://github.com/learnzdevelopmenthub/paadhai/tree/main/.claude/skills/dev-audit
Command: npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers a disciplined pull request audit so architecture, security, and compatibility risks are surfaced before merge approvals even when CI is green and the codebase grows in complexity.

Core Features & Use Cases

  • Seven-step workflow: Gathers context from branch names, .paadhai.json, and issue plans, verifies CI status, captures diffs, and funnels everything into a unified audit report.
  • Three independent reviews: Runs architecture, security, and compatibility analyses in parallel using the structured reviewer prompt, then synthesizes findings with PASS/FAIL results and detailed evidence.
  • Human sign-off and handoff: Pauses for explicit approval, then shares the structured audit summary and next steps so the release pipeline can continue confidently.
  • Use Case: Ideal for a developer or reviewer finishing a feature branch who needs to ensure architectural alignment, surface security gaps, and confirm compatibility before handing the PR off to the release process.

Quick Start

Run dev-audit on the current PR to gather architecture, security, and compatibility findings before merging.

Frequently Asked Questions about dev-audit

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

FAQPage Schema
How do I audit a GitHub pull request for architecture, security, and compatibility risks before merging?

A pull request audit evaluates architecture, security, and compatibility risks by capturing diffs, verifying CI checks, and applying structured reviewer prompts. It synthesizes findings into PASS or FAIL results with evidence before signaling safe merge approval.

Can I automate code review checks to require explicit human sign-off before a release continues?

Yes, the workflow pauses for explicit human sign-off after generating architecture, security, and compatibility findings. It shares a structured audit summary and next steps only after an approver explicitly authorizes the release pipeline to continue.

Does the pull request audit work with feature, fix, and emergency branches?

Yes, the pull request audit applies to feature, fix, and emergency branches. It gathers context directly from branch names and the repository's .paadhai.json configuration file to ensure the review process adapts to various branch workflows.

What is the best way to surface security gaps in a pull request when CI checks are green?

The best way to surface security gaps when CI is green is running independent architecture, security, and compatibility analyses in parallel. This synthesizes structured findings with evidence, identifying merge risks that automated CI checks miss.

How do I configure repository settings for a three-dimension PR audit?

You configure repository settings for a PR audit by defining parameters in the .paadhai.json configuration file. The audit workflow reads this file alongside branch names and issue plans to gather context and apply structured reviewer prompt criteria.