afya-sahihi-review

Blocks Afya Sahihi PRs violating non-negotiable security, coupling, async discipline, and test adequacy checks.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/AmosBunde/Afya-Sahihi --skill afya-sahihi-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: afya-sahihi-review
Source: https://github.com/AmosBunde/Afya-Sahihi/tree/main/skills/afya-sahihi-review
Command: npx skills add https://github.com/AmosBunde/Afya-Sahihi --skill afya-sahihi-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies a comprehensive pull request review bar to enforce security, coupling, async discipline, and testing standards that pre-commit hooks cannot enforce, ensuring patient-safe software practices.

Core Features & Use Cases

  • Enforces security review, tight-coupling detection, secure code patterns, async discipline, and test adequacy for Afya Sahihi PRs.
  • Provides a consistent, auditable reviewer workflow that can be followed by humans and AI assistants.
  • Use Case: When assessing a PR, apply the playbook to block changes that would introduce PHI exposure, brittle coupling, or insufficient tests.

Quick Start

Review the current PR diff using these guidelines to determine blockers and require remediation.

Frequently Asked Questions about afya-sahihi-review

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

FAQPage Schema
How do I enforce security and test adequacy standards during pull request reviews?

A pull request review playbook blocks PRs violating non-negotiables by detailing security, tight-coupling detection, async discipline, and test adequacy checks to ensure patient-safe software practices.

What is async discipline in code review and how does it prevent patient data exposure?

Async discipline in code review verifies that asynchronous operations handle data safely without race conditions or leaks. A review playbook enforces this by checking async patterns to prevent PHI exposure and ensure patient-safe software.

How do I review a PR diff to block tight-coupling and insufficient test coverage?

Reviewing a PR diff to block tight-coupling and insufficient tests involves applying documented reviewer guidance to identify brittle dependencies, enforce test adequacy, and generate actionable remediation steps for audit-ready governance.

Can I use an AI assistant to automate security review and governance checks for healthcare PRs?

Yes, you can use an AI assistant to automate security review and governance checks. The playbook provides a consistent, auditable workflow that both human reviewers and AI assistants can follow to enforce non-negotiables and patient-safe practices.

Why do pre-commit hooks fail to enforce coupling and async discipline standards?

Pre-commit hooks fail to enforce coupling and async discipline standards because they operate locally on file syntax rather than analyzing architectural dependencies or complex asynchronous runtime behaviors across the entire PR diff.