qa-reviewer

Name: qa-reviewer
Availability: InStock
Author: bayyo1337

Automate QA review and validate Git commits for the hka-agentic-raumzeit-bot project.

1|Updated Apr 9, 2026

Search Tags:#git #testing #commit #qa #review #edge-cases #ci

Ready to run

npx skills add https://github.com/Bayyo1337/hka-agentic-raumzeit-bot --skill qa-reviewer-bayyo1337

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-reviewer
Source: https://github.com/Bayyo1337/hka-agentic-raumzeit-bot/tree/main/.gemini/skills/qa-reviewer
Command: npx skills add https://github.com/Bayyo1337/hka-agentic-raumzeit-bot --skill qa-reviewer-bayyo1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independent QA and Git commit validation prevent regressions when applying fixes to the hka-agentic-raumzeit-bot by ensuring changes are verified, documented, and ready for safe integration.

Core Features & Use Cases

Independent review of fixes from the issue-fixer, with context from the project logs.
Diff analysis against HEAD to detect unintended side effects and ensure conformance with project mandates (gemini guidelines).
Final integration testing orchestration including E2E checks, linting, and controlled commits to maintain repository health when delivering changes.

Quick Start

Review the latest session_log.md, validate all diffs, and ensure fixes pass tests before committing.

Frequently Asked Questions about qa-reviewer

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

FAQPage Schema

How do I automate QA review and ensure clean Git commits after applying fixes?▼

Final integration testing for clean commits involves orchestrating E2E checks, linting, and edge-case validation. This workflow ensures all changes pass tests and are verified against project logs before executing controlled Git commits to prevent regressions.

How does diff analysis against HEAD detect unintended side effects during code review?▼

Diff analysis against HEAD inspects staged and unstaged changes to catch unintended side effects before committing. It verifies that fixes conform to project mandates and ensures no regressions are introduced into the codebase during integration.

Can I use automated QA review to validate edge cases before a controlled Git commit?▼

Yes, automated QA review validates edge cases by running structured test orchestration and E2E checks. It ensures fixes pass all tests and linting before guiding controlled Git commits to maintain repository health and prevent regressions.

What is the best way to prevent regressions when integrating fixes into a CI workflow?▼

The best way to prevent regressions in CI is applying independent quality control that orchestrates E2E checks and linting. Validating session logs and diffs before committing ensures changes are verified and safe for final integration.

Do I need session logs to run independent quality control on issue fixes?▼

Yes, you need session logs like session_log.md to provide context for independent review. Reviewing these logs allows the QA process to validate fixes accurately and ensure changes are documented and ready for safe integration.