agentleFS
KadirHarmancKadirHarmanc/nazar-skill/skills/preflight/SKILL.md

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

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.
  • asterkinSkill

    adr

    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

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 5 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • AnthropicSkill

    status

    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

  • GitHubSkill

    refactor

    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

  • DockerSkill

    review-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

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
  1. Distinctive:

    Run comprehensive App Store and Play Store compliance checks before submission.

    line 7
  2. Very specific:

    Call the nazar-skill:preflight agent with:

    line 40
  3. Distinctive:

    Check each rule against the project files

    line 46

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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):

  • *.xcodeproj or *.xcworkspace
  • Podfile or Podfile.lock
  • Info.plist
  • *.swift source files
  • Package.swift (Swift Package Manager)
  • Cartfile (Carthage)

Android indicators (check for ANY of these):

  • build.gradle or build.gradle.kts
  • AndroidManifest.xml
  • *.kt or *.java source files in standard Android paths
  • settings.gradle or settings.gradle.kts
  • gradlew

Cross-platform (both) (check for ANY of these):

  • React Native: package.json with react-native dependency + ios/ and android/ directories
  • Flutter: pubspec.yaml with flutter dependency + ios/ and android/ directories
  • Kotlin Multiplatform: shared/ directory with commonMain
  • Capacitor/Ionic: capacitor.config.ts or capacitor.config.json
  • .NET MAUI: *.csproj with MAUI references
  • Xamarin: *.sln with iOS and Android projects

Step 2: Dispatch Preflight Agent

Call the nazar-skill:preflight agent with:

  • platform: ios, android, or both
  • project_path: the root directory of the project

The agent will:

  1. Load the appropriate rule files from ~/.claude/plugins/nazar-skill/skills/preflight/rules/
  2. Check each rule against the project files
  3. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.