skills.rest
AoManoh
AoManohCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Execute E2E UI tests, API tests, and static code reviews to generate evidence-based QA reports.

Updated Apr 15, 2026
Search Tags:#root cause analysis#qa#e2e testing#api testing#evidence report#static review#lifecycle governance
One-click install
npx skills add https://github.com/AoManoh/project_templates --skill code-review-aomanoh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/AoManoh/project_templates/tree/main/skills/code-review
Command: npx skills add https://github.com/AoManoh/project_templates --skill code-review-aomanoh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures AI-performed QA activities generate consistent, evidence-backed E2E/API testing outputs and static review findings, each with traceable root-cause and followable lifecycle status.

Core Features & Use Cases

  • E2E & API testing with evidence chains: Collects snapshots, screenshots, network request/response details, and console logs as required, then turns results into structured bug entries.
  • Source-level root-cause tracing: Uses a semantic code search workflow (and falls back to direct file viewing) to connect observed failures to the actual implementation lines.
  • Static code review with risk grading: Reviews the intended diff scope for safety, concurrency/resource safety, performance, data consistency, error handling, architectural boundaries, and documentation/test gaps, then merges and classifies conclusions.

Quick Start

Trigger a QA run by asking the AI to perform code review and E2E/API tests, then generate the report under docs/code-review with evidence and root-cause analysis.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I generate evidence-based QA reports with root-cause analysis?▼

To generate evidence-based QA reports, trigger an E2E UI and API interface test run. The system collects snapshots and network logs, connects observed failures to source-level implementation lines, and outputs structured bug entries under docs/code-review.

What is source-level root-cause tracing in static code review?▼

Source-level root-cause tracing is a mechanism that uses semantic code search to connect observed test failures directly to actual implementation lines. It falls back to direct file viewing to ensure reproducible defect discovery during software delivery.

Can I use E2E testing and API interface tests for change verification?▼

Yes, you can use E2E UI testing and API interface tests for change verification. The process executes these tests alongside static code reviews to enforce SPEC.md compliance, capturing console logs and network requests to document reproducibility.

Does static code review include risk grading for concurrency and data consistency?▼

Yes, static code review includes risk grading for concurrency and data consistency. It evaluates intended diff scopes for safety, performance, error handling, architectural boundaries, and documentation gaps, then merges and classifies conclusions.

What is the best way to enforce lifecycle governance and severity states in bug reports?▼

The best way to enforce lifecycle governance and severity states in bug reports is to apply a structured QA workflow that mandates five specific issue elements. This ensures every static review finding and test failure maintains followable lifecycle status.

Why does my E2E testing output lack traceable root-cause documentation?▼

Your E2E testing output lacks traceable root-cause documentation without a structured evidence chain. Applying a semantic code search workflow connects observed failures to actual implementation lines, enforcing SPEC.md compliance for reproducibility.

Related Skills

Explore More Software Engineering Skills→
erfanzarerfanzar
27

requesting-code-review

Automate pre-commit code review with static checks, linting, and auto-fixes.

Community
Advanced
GitnappGitnapp

garage-elys-agent-governance

Synchronize GitHub issue and pull request governance metadata for development workflows.

Community
Advanced
lv7devlv7dev

Root Cause Tracing

Trace call stacks backward to identify original bug triggers.

Community
Advanced
tiweentiween

bmad-tea

Implement risk-based testing strategies, quality gates, and scalable test frameworks.

Official
Advanced