preflight
Skill0 starsChanged 8 months agoMITView on GitHub
Run App Store and Play Store pre-submission checks. Use when user says 'preflight', 'store check', 'app store kontrol', 'play store kontrol', 'yayinlamadan once kontrol', 'store rejection'.
47 other projects use a version of this.
Adopted by
Most recently taken up by
- sohaibt/product-modetheir own version, first seen Nov 8, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- codiume/skillstheir own version, first seen Nov 8, 2026
- me2resh/apexyardtheir own version, first seen Nov 1, 2026
- vzhukovs/podman-desktop-kittheir own version, first seen Nov 1, 2026
- khgouldy/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use adr, ship and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 5 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
Other versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- webiny/webiny-js★ 8ksame name
- CrowdDotDev/crowd.dev★ 3.4ksame name
- tphakala/birdnet-go★ 2.4ksame name
- openfootmanager/openfootmanager★ 1.2ksame name
- mohebifar/tooscut★ 716same name
- me2resh/apexyard★ 542same name
- linuxfoundation/insights★ 288same name
- sohaibt/product-mode★ 176same name
- unlearndev/skills★ 101same name
- ogulcancelik/agent-skills★ 81same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- batchSkill
- code-qualitySkill
- complianceSkill
- coverageSkill
- fixSkill
- healthSkill
- live-testSkill
- reportSkill
- scanSkill
- security-auditSkill
- yaml-genSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 42 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Run comprehensive App Store and Play Store compliance checks before submission.
- Very specific: line 40
Call the nazar-skill:preflight agent with:
- Distinctive: line 46
Check each rule against the project files
“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nazar Preflight Skill
Run comprehensive App Store and Play Store compliance checks before submission.
Instructions
Step 1: Detect Platform
Scan the project directory to determine the platform:
iOS indicators (check for ANY of these):
*.xcodeprojor*.xcworkspacePodfileorPodfile.lockInfo.plist*.swiftsource filesPackage.swift(Swift Package Manager)Cartfile(Carthage)
Android indicators (check for ANY of these):
build.gradleorbuild.gradle.ktsAndroidManifest.xml*.ktor*.javasource files in standard Android pathssettings.gradleorsettings.gradle.ktsgradlew
Cross-platform (both) (check for ANY of these):
- React Native:
package.jsonwithreact-nativedependency +ios/andandroid/directories - Flutter:
pubspec.yamlwithflutterdependency +ios/andandroid/directories - Kotlin Multiplatform:
shared/directory withcommonMain - Capacitor/Ionic:
capacitor.config.tsorcapacitor.config.json - .NET MAUI:
*.csprojwith MAUI references - Xamarin:
*.slnwith iOS and Android projects
Step 2: Dispatch Preflight Agent
Call the nazar-skill:preflight agent with:
- platform:
ios,android, orboth - project_path: the root directory of the project
The agent will:
- Load the appropriate rule files from
~/.claude/plugins/nazar-skill/skills/preflight/rules/ - Check each rule against the project files
- Return pass/fail results per rule
Step 3: Present Results
Format the output as follows:
=== NAZAR PREFLIGHT REPORT ===
Platform: [iOS / Android / Both]
Project: [project path]
Date: [current date]
--- READINESS SCORE ---
iOS: XX/22 passed (XX%)
Android: XX/12 passed (XX%)
--- BLOCKING ISSUES (must fix before submission) ---
[FAIL] Rule X: Rule Name
File: /path/to/file.ext (line XX)
Issue: Description of what is wrong
Fix: How to fix it
[FAIL] Rule Y: Rule Name
...
--- WARNINGS (recommended to fix) ---
[WARN] Rule Z: Rule Name
...
--- PASSED ---
[PASS] Rule A: Rule Name
[PASS] Rule B: Rule Name
...
--- FIX SUGGESTIONS (prioritized) ---
1. [BLOCKING] Fix description (Rule X)
2. [BLOCKING] Fix description (Rule Y)
3. [RECOMMENDED] Fix description (Rule Z)Step 4: Categorize Issues
BLOCKING (will cause rejection):
- Missing privacy manifest (iOS)
- Missing permission descriptions (iOS)
- UIWebView usage (iOS)
- targetSdkVersion too low (Android)
- debuggable=true in release (Android)
- Missing exported attribute (Android)
- Missing account deletion (Android, if accounts exist)
WARNINGS (may cause rejection or poor review):
- Force unwrap abuse (iOS)
- Placeholder content (both)
- ProGuard not enabled (Android)
- Content rating considerations (Android)
- ATS blanket exceptions (iOS)
- Unencrypted storage (Android)
Platform-Specific File Paths
React Native projects:
- iOS files:
ios/[ProjectName]/Info.plist,ios/Podfile,ios/[ProjectName].xcodeproj - Android files:
android/app/build.gradle,android/app/src/main/AndroidManifest.xml
Flutter projects:
- iOS files:
ios/Runner/Info.plist,ios/Podfile,ios/Runner.xcodeproj - Android files:
android/app/build.gradle,android/app/src/main/AndroidManifest.xml
Native iOS: files at project root or in app target directory
Native Android: files in app/ directory typically
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.

