rcode-fatima-qa

Generate tests and QA artifacts for implemented features.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-fatima-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-fatima-qa
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/agents/fatima-qa
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-fatima-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you verify implemented features quickly by creating realistic tests, finding edge cases, triaging bugs, and making release decisions based on quality evidence instead of guesswork.

Core Features & Use Cases

  • Test generation: Creates unit, integration, API, and end-to-end tests for existing code using standard framework patterns.
  • Edge-case hunting: Looks for failure modes, regressions, and risky inputs that happy-path checks often miss.
  • Bug triage and release gating: Produces structured bug reports, evaluates severity, and determines whether a release is ready to ship.
  • Use case: A developer asks for coverage on a new login flow, and this Skill generates meaningful tests, checks acceptance criteria, and flags blocking issues before release.

Quick Start

Ask Fatima to generate tests for a specific feature and include the target file, framework, and acceptance criteria.

Frequently Asked Questions about rcode-fatima-qa

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

FAQPage Schema
How do I generate unit and integration tests for existing code?

You can generate unit, integration, API, and end-to-end tests for existing code by providing the target file, standard test framework patterns, and acceptance criteria to produce meaningful test coverage.

What is the best way to find edge cases and coverage gaps in a new feature?

Edge-case hunting identifies failure modes, regressions, and risky inputs that happy-path checks often miss by analyzing implemented features against their acceptance criteria to pinpoint test coverage gaps.

How do I triage bugs and make release gating decisions based on quality evidence?

Bug triage produces structured bug reports, evaluates severity, and executes explicit go or no-go quality checks to determine whether a release is ready to ship based on evidence.

Does test generation work with my existing test framework patterns?

Yes, test generation applies to existing code by requiring standard test framework patterns and acceptance-criteria verification to create realistic unit, integration, API, and end-to-end tests.

When do I need to verify acceptance criteria before a release?

Acceptance-criteria verification is needed before release gating to ensure implemented features pass explicit go or no-go quality checks and blocking issues are flagged.

Why does happy-path testing miss risky inputs and regressions?

Happy-path testing misses risky inputs because it lacks edge-case hunting, which actively looks for failure modes and regressions by challenging code with non-standard scenarios.