qa-test-staging
Skill227 starsChanged 50 days agoMITView on GitHub
Runs the Compass post-deploy staging confidence sweep in a user-connected browser, verifies the expected signed-in test profile, exercises core flows, checks console/network failures, and reports evidence. Use when explicitly invoked with /qa-test-staging.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- chaosSkill
- google-sync-debugSkill
- shipSkill
- simplifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 11 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Do not substitute an isolated browser when a signed-in profile is required.
- Very specific: line 37
Test https://staging.compasscalendar.com in a user-connected browser after a deploy.
- Distinctive: line 44
Do not enter credentials or automate Google OAuth.
- Distinctive: line 45
Do not guess which browser profile is correct.
- Distinctive: line 46
Verify signed-in state from the account control before changing data.
- Distinctive: line 47
Never fall back to a temporary account and report an authenticated pass.
- Distinctive: line 48
Stop and ask the user to connect/sign in the staging profile when no suitable session is available.
- Distinctive: line 50
Do not delete created artifacts without explicit approval.
- Distinctive: line 62
If multiple valid sessions exist, ask the user which to use.
- Distinctive: line 91
Read its summary and completed validation/test evidence.
- Distinctive: line 96
Do not revive stale unchecked manual-testing sections as requirements.
- Very specific: line 100
Run anonymous coverage only when a separate connected profile visibly reports Temporary account.
- Very specific: line 105
After Booking WP-08 is on staging, also load https://staging.compasscalendar.com/book/<slug> as a guest (no login).
- Distinctive: line 108
Never enter credentials for this path.
- Distinctive: line 121
Ask whether to remove created artifacts.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When
Explicitly invoked with /qa-test-staging after a staging deploy.
Steps
Select signed-in browser → core sweep → changed flows → anonymous sweep → report.
Output
Evidence of staging confidence; console/network notes.
Pass
Expected test profile verified; core flows exercised.
Anti-patterns
Do not substitute an isolated browser when a signed-in profile is required.
See anti-patterns.md.
Escalate
Wrong profile, staging down, or credentials the agent must not enter.
Test Compass staging
Test https://staging.compasscalendar.com in a user-connected browser after a
deploy. Prefer Cursor's browser control in Cursor, Claude-in-Chrome in Claude,
or another real-profile browser tool. Do not substitute an isolated browser
when the flow depends on an existing signed-in profile.
Safety boundaries
- Do not enter credentials or automate Google OAuth.
- Do not guess which browser profile is correct.
- Verify signed-in state from the account control before changing data.
- Never fall back to a temporary account and report an authenticated pass.
- Stop and ask the user to connect/sign in the staging profile when no suitable session is available.
- Do not delete created artifacts without explicit approval.
Expected authenticated test account: compasscaltest3@gmail.com.
Temporary account indicates the anonymous/local profile.
1. Select and verify the browser
- List connected browser tabs/profiles using the available browser tooling.
- Navigate a fresh tab to staging.
- Inspect the account control:
- expected test email → proceed
Temporary account→ this is not the authenticated target
- If multiple valid sessions exist, ask the user which to use. If none exist, stop with the exact connection/sign-in action required.
- Lock the selected tab/session when the browser tool supports locking.
2. Core authenticated sweep
Confirm each action from rendered state, not merely a successful click. Capture a screenshot when supported and inspect console/network errors throughout.
- Load and auth — staging renders and the expected account remains shown.
- Calendar event — create a uniquely named timed event, move or resize it, open its details, switch Day/Week views, reload, and confirm persistence.
- Navigation — previous/next date, month navigation, and date-picker jump.
- Commands — open the command palette and shortcuts panel; complete one palette action end-to-end.
- Google state — observe connection/import status without reconnecting or mutating OAuth unless the user explicitly requested that scenario.
A visually successful flow with a thrown exception or failed request is a finding.
3. Recently changed flows
Inspect recently merged pull requests against main with gh. Select the
deploy window the user named; if no window was given, cover the latest relevant
merge rather than guessing a large range.
For each selected pull request:
- Read its summary and completed validation/test evidence.
- Derive the user-visible flow changed.
- Replay that flow on staging.
- Attribute any regression to the pull request only when evidence supports it.
Do not revive stale unchecked manual-testing sections as requirements.
4. Anonymous sweep
Run anonymous coverage only when a separate connected profile visibly reports
Temporary account. Recheck the core create/edit/persistence behavior there,
then return to the authenticated profile. If unavailable, report it as skipped,
not failed.
After Booking WP-08 is on staging, also load
https://staging.compasscalendar.com/book/<slug> as a guest (no login).
Confirm the public page renders or 404s when the host page is disabled.
Never enter credentials for this path.
5. Report and cleanup
Report:
- Objective breakage — flow, observable failure, console/network evidence, screenshot, and related pull request when established
- Worth review — visual or interaction concerns requiring judgment
- Clean — exact flows completed
- browser/profile identity, account state, and any skipped coverage
- artifacts created during testing
Ask whether to remove created artifacts. If approved, use the app's visible delete controls, reload, and confirm deletion persisted. Unlock the browser tab when finished.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

