beta-testing-propertyiq

Scan the PropertyIQ codebase and validate end-to-end user journeys across tiers.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/jimbrig/Realestate --skill beta-testing-propertyiq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beta-testing-propertyiq
Source: https://github.com/jimbrig/Realestate/tree/main/.claude/skills/beta-testing-propertyiq
Command: npx skills add https://github.com/jimbrig/Realestate --skill beta-testing-propertyiq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

PropertyIQ's beta-testing skill automates comprehensive QA by dynamically discovering testable surfaces and validating end-to-end user journeys across tiers, reducing manual test planning and oversight.

Core Features & Use Cases

  • Self-discovery of routes, APIs, components, and config at runtime for test coverage.
  • Cross-tier testing (public, auth, admin) to verify gating, entitlement propagation, and CTA placement.
  • Automatic submission of discovered issues to the beta feedback tracking system via the /api/betatest/feedback API.

Quick Start

Run the beta-testing-propertyiq skill to bootstrap an isolated test environment and begin automated beta testing.

Frequently Asked Questions about beta-testing-propertyiq

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

FAQPage Schema
How do I automate end-to-end QA testing across multiple user tiers?

Automated end-to-end QA testing across multiple user tiers requires scanning the live codebase to discover testable surfaces and validating user journeys across public, authenticated, and admin tiers. This skill verifies gating, entitlements, and CTA placement dynamically at runtime.

How does Playwright discover routes and APIs for test coverage?

Playwright discovers routes and APIs for test coverage by scanning the live PropertyIQ codebase at runtime to self-discover routes, APIs, components, and configurations. This dynamic discovery reduces manual test planning and validates end-to-end user journeys automatically.

Do I need an isolated test environment to run automated beta testing?

Yes, you need an isolated test environment to run automated beta testing. The skill requires a configured isolated test environment and a bootstrap script to initialize the worktree and capture tester tokens for issue submission.

How do I automatically submit discovered issues to a beta feedback tracker?

Automatically submit discovered issues to a beta feedback tracker by using the provided API endpoint. The skill submits found issues via the /api/betatest/feedback API after validating end-to-end user journeys and auditing data provenance and gating.

What is the best way to audit data provenance and gating in a web application?

Auditing data provenance and gating in a web application is best handled by scanning the live codebase to discover testable surfaces and validating cross-tier user journeys. This approach verifies entitlement propagation and gating across public, authenticated, and admin surfaces.