pr-preview-shipping
Skill1 starsChanged 28 days agoBSD-3-ClauseView on GitHub
Makes every PR produce an installable or clickable preview within minutes, per stack. Use when reviewing CI/CD for mobile, web or API projects, or when someone says to pull the branch and run it. Based on Alberto Moedano (Code with Beto).
In this repository52 other files it gives its agents.
- academic-research-assistantSkill
- answer-sheetSkill
- app-graphicsSkill
- app-landing-pageSkill
- app-screenshotsSkill
- break-uiSkill
- consumer-app-from-behaviorSkill
- cross-language-safetySkill
- dart-tool-scriptsSkill
- decision-sweepSkill
- engineering-diarySkill
- figma-review-loopSkill
- flutter-app-size-auditSkill
- flutter-async-at-the-edgeSkill
- flutter-async-cubit-safetySkill
- flutter-bloc-clean-architectureSkill
- flutter-clean-architecture-tddSkill
- flutter-cubit-smart-cachingSkill
- flutter-error-logging-conventionsSkill
- flutter-observability-instrumentationSkill
- flutter-paywall-and-review-timingSkill
- flutter-precommit-cleanupSkill
- flutter-router-decisionSkill
- flutter-runtime-safetySkill
- flutter-shorebird-otaSkill
- flutter-stream-architectureSkill
- flutter-strict-analysisSkill
- flutter-web-first-paintSkill
- forced-pivot-15-daySkill
- gplay-consoleSkill
- ios-distribution-feature-flagsSkill
- launch-readinessSkill
- launch-watchSkill
- locale-expert-reviewSkill
- market-pulseSkill
- mobile-ui-referenceSkill
- moscow-prioritizationSkill
- orchestrate-agentic-engineeringSkill
- parallel-agent-inboxSkill
- paywall-conversion-flowSkill
- paywall-transparencySkill
- proactive-crash-repair-loopSkill
- promise-auditSkill
- ship-first-dollar-appSkill
- slim-ios-simulator-fleetSkill
- spec-sql-harnessSkill
- store-launch-mastermindSkill
- sync-contextSkill
- task-blitzSkill
- techdebtSkill
- vendor-decisionSkill
- web-interface-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If a stakeholder, QA, or future-you needs to "pull and run" to review, the loop is too slow.
≈ “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
PR-Preview Shipping
Principle
If a stakeholder, QA, or future-you needs to "pull and run" to review, the loop is too slow. Every PR yields a clickable preview.
Per-stack recipe
| Stack | Preview channel |
| Mobile app | Firebase App Distribution per PR, or TestFlight internal |
| Mobile app (Android) | Firebase App Distribution + signed APK |
| Mobile + serverless backend | TestFlight internal, plus a per-PR backend staging URL |
| Desktop app | Pre-release artifact, for example on GitHub Releases |
| SSR web framework | Host preview deployment, for example Cloudflare Pages |
| API server | Tunnel preview against the PR branch |
Required PR comment
✅ Preview ready
• iOS: TestFlight internal group (build N)
• Web: {branch}.{project}.pages.dev
• Notes: {what changed}App Store Connect documents no per-build link for internal builds.
Internal testers install from the TestFlight app after the build is added to their group.
Cloudflare Pages preview aliases are per branch (<branch>.<project>.pages.dev, lowercased, non-alphanumerics become -), not per PR number.
Acceptance
- Push → preview link <90s web, <12min iOS.
- Preview shows branch + short SHA in about screen.
- Zero manual reviewer setup.
Sources
- Alberto Moedano (Code with Beto), LinkedIn post: https://www.linkedin.com/feed/update/urn:li:activity:7398756359166599168/
- https://developer.apple.com/help/app-store-connect/test-a-beta-version/add-internal-testers
- https://developers.cloudflare.com/pages/configuration/preview-deployments/
- https://firebase.google.com/docs/app-distribution
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.

