staff-qa

Assess test quality and regression risk for Zinero monorepo changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/FernandoBade/zinero-hack-your-expenses --skill staff-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: staff-qa
Source: https://github.com/FernandoBade/zinero-hack-your-expenses/tree/main/skills/staff-qa
Command: npx skills add https://github.com/FernandoBade/zinero-hack-your-expenses --skill staff-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a guardrail for test quality, coverage relevance, and regression confidence across the Zinero monorepo by defining expectations and checkpoints for backend and frontend testing.

Core Features & Use Cases

  • Guided evaluation of unit, integration, and end-to-end tests against shared contracts and project patterns.
  • Risk identification and regression-risk scoring for proposed changes.
  • Cross-layer verification coordination between backend and frontend teams.

Quick Start

Describe a change and I will assess its testability, coverage, and regression risk.

Frequently Asked Questions about staff-qa

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

FAQPage Schema
How do I improve test quality and regression confidence across backend and frontend?

To improve test quality and regression confidence, you can evaluate unit, integration, and end-to-end tests against shared contracts and existing project patterns to identify coverage gaps and risks.

What is regression-risk scoring for proposed software changes?

Regression-risk scoring assesses proposed changes by identifying potential risks and evaluating testability, ensuring that modifications align with applicable risk mitigations before implementation.

How do I assess the testability and coverage of a new code change?

You can assess testability and coverage by describing the change to evaluate its regression risk, check alignment with shared contracts, and identify missing verification planning.

Does this approach support cross-layer verification coordination between teams?

Yes, cross-layer verification coordination is supported, enabling backend and frontend teams to align test strategies and ensure shared contracts are validated across the monorepo.

What is the best way to evaluate end-to-end tests against shared contracts?

The best way to evaluate end-to-end tests is through guided evaluation that checks them against established shared contracts and existing test patterns within the project.

When do I need verification planning for changes in a monorepo?

You need verification planning for monorepo changes when proposing modifications that require alignment with shared contracts, risk mitigations, and existing test patterns to prevent regressions.