pre-flight-check 1.2.0__tar.gz

pre_flight_check-1.2.0/.claude-plugin/marketplace.json

@@ -0,0 +1,17 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "pre-flight-check",
+  "description": "Stop your AI agent from declaring 'done' on broken code. Fail-fast quality gate that runs Typecheck, Lint, Test, and Security Audit sequentially before any task is marked complete.",
+  "owner": {
+    "name": "mirekondro",
+    "url": "https://github.com/mirekondro"
+  },
+  "plugins": [
+    {
+      "name": "pre-flight-check",
+      "description": "Fail-fast Typecheck → Lint → Test → Security Audit gate. Auto-detects Node.js and Python. Forbids the agent from suppressing errors. Zero runtime dependencies.",
+      "source": "./",
+      "category": "quality"
+    }
+  ]
+}

pre_flight_check-1.2.0/.claude-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "pre-flight-check",
+  "description": "Fail-fast quality gate (Typecheck → Lint → Test → Security Audit) that runs before any task is declared done or code is committed. Auto-detects Node.js and Python projects.",
+  "author": {
+    "name": "mirekondro",
+    "url": "https://github.com/mirekondro"
+  },
+  "homepage": "https://github.com/mirekondro/The-Pre-Flight-Check",
+  "license": "MIT"
+}

pre_flight_check-1.2.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,105 @@
+name: 🐛 Bug report
+description: Something doesn't work as documented.
+title: "[bug] "
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the report. The more concrete you can be, the faster this gets fixed. Paste raw output rather than describing it.
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Tell us what you ran and what you saw. One paragraph is fine.
+      placeholder: |
+        I ran `python3 ~/.claude/skills/pre-flight-check/scripts/run-pipeline.py` in a pnpm monorepo and it picked npm instead of pnpm.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect?
+      placeholder: |
+        Detect pnpm-lock.yaml at the root, use `pnpm` for all stages.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Minimal reproduction
+      description: Exact commands. If you can pin it to one of the fixtures under `examples/`, even better.
+      render: bash
+      placeholder: |
+        cd ~/projects/my-repo
+        python3 ~/.claude/skills/pre-flight-check/scripts/run-pipeline.py
+    validations:
+      required: true
+
+  - type: textarea
+    id: full-output
+    attributes:
+      label: Full pipeline output
+      description: Everything from the first `# Pre-Flight Check` line through the final `### ❌` / `### ✅` / `### ⚠️` block. Paste raw, do not summarise.
+      render: text
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: OS + version
+      placeholder: macOS 14.5 / Ubuntu 22.04 / Windows 11
+    validations:
+      required: true
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python version
+      description: Output of `python3 --version`.
+      placeholder: Python 3.11.7
+    validations:
+      required: true
+
+  - type: input
+    id: claude-version
+    attributes:
+      label: Claude Code version
+      description: Output of `claude --version`. Optional if unsure.
+      placeholder: claude 1.x.x
+
+  - type: input
+    id: skill-version
+    attributes:
+      label: Skill version / commit
+      description: First line of `~/.claude/skills/pre-flight-check/scripts/run-pipeline.py`, or the commit sha you installed from.
+      placeholder: main @ 3592de9
+
+  - type: dropdown
+    id: install-method
+    attributes:
+      label: How did you install the skill?
+      options:
+        - One-line install (curl|bash)
+        - One-line install (irm|iex)
+        - Local clone + install.sh
+        - Manual cp
+        - Other (describe in "What happened?")
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: pre-flight
+    attributes:
+      label: Pre-submission checklist
+      options:
+        - label: I searched existing issues and didn't find a duplicate.
+          required: true
+        - label: I'm running Python ≥3.8.
+          required: true
+        - label: The output above is raw, complete, and unredacted (modulo absolute paths you'd rather not share).
+          required: true

pre_flight_check-1.2.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📖 Documentation
+    url: https://github.com/mirekondro1/The-Pre-Flight-Check#readme
+    about: Install guide, supported runtimes, FAQ.
+  - name: 🛠️ Troubleshooting
+    url: https://github.com/mirekondro1/The-Pre-Flight-Check/blob/main/INSTALL.md#troubleshooting
+    about: 9 common failure modes with copy-paste fixes. Check here before opening a bug report.
+  - name: 🤝 Contributing
+    url: https://github.com/mirekondro1/The-Pre-Flight-Check/blob/main/CONTRIBUTING.md
+    about: How to add a new runtime adapter, fixture, or doc fix.

pre_flight_check-1.2.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,82 @@
+name: 💡 Feature request
+description: Propose a new capability before opening a PR.
+title: "[feat] "
+labels: ["enhancement", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Read [CONTRIBUTING.md → Project philosophy](../blob/main/CONTRIBUTING.md#project-philosophy) before filing. **Especially** the "What we don't want" list — proposals for new dependencies, config files, or auto-installing tools will be declined.
+
+        New runtime adapters and new fixtures are welcome and rarely need long discussion. Behavioral changes to existing stages or to the failure-block format need agreement first.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What user-visible problem does this solve? Be concrete — name a real workflow.
+      placeholder: |
+        I work in a Go monorepo. `pre-flight-check` exits with UNKNOWN RUNTIME so my agent skips quality gates entirely.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: What change do you want? Include the expected command(s) per stage if it's a new runtime.
+      placeholder: |
+        Add a Go adapter that detects `go.mod` and runs:
+          1. TYPECHECK     -> go vet ./...
+          2. LINT          -> golangci-lint run
+          3. TEST          -> go test ./...
+          4. SECURITY AUDIT -> govulncheck ./...
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: What else could solve the problem? Why is your proposal better?
+      placeholder: |
+        - Manually invoking each tool from a Makefile: doesn't enforce the agent contract.
+        - Project-local skill fork: works but doesn't help anyone else.
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Category
+      options:
+        - New runtime adapter
+        - New stage / tool for an existing runtime
+        - Failure-block format change
+        - Installer change
+        - Documentation
+        - New fixture
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope check
+      description: |
+        Tick whichever apply. Honesty saves us both time.
+      value: |
+        - [ ] This adds **no** Python runtime dependencies.
+        - [ ] This adds **no** configuration file.
+        - [ ] This does **not** install third-party tooling on behalf of the user.
+        - [ ] This does **not** change the failure-block Markdown shape (### ❌ FAILURE, **Command Executed:**, **Context for AI Fix:**).
+        - [ ] I'm willing to send the PR if accepted.
+
+  - type: checkboxes
+    id: pre-flight
+    attributes:
+      label: Pre-submission checklist
+      options:
+        - label: I read CONTRIBUTING.md and my proposal aligns with the project philosophy.
+          required: true
+        - label: I searched existing issues and didn't find a duplicate or rejected version of this.
+          required: true

pre_flight_check-1.2.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,68 @@
+<!--
+Thanks for the PR. Fill out the sections below — terse is fine, blank is not.
+For docs-only or typo fixes, you can skip the Test plan section.
+-->
+
+## Summary
+
+<!-- One paragraph. What does this change and why. Link the issue it resolves. -->
+
+Closes #
+
+## Type
+
+- [ ] 🐛 Bug fix (non-breaking)
+- [ ] ✨ New feature (non-breaking — new runtime, new fixture, new flag)
+- [ ] 💥 Breaking change (alters failure-block format, removes flag, changes default behavior)
+- [ ] 📖 Documentation only
+- [ ] 🛠️ Build / CI / installer change
+- [ ] ♻️ Refactor (no behavior change)
+
+## Scope checklist
+
+<!-- Project philosophy gates — read CONTRIBUTING.md if any of these don't apply. -->
+
+- [ ] No new Python runtime dependencies added to `run-pipeline.py`.
+- [ ] No new configuration file introduced.
+- [ ] No third-party tooling auto-installed on behalf of the user.
+- [ ] If the failure-block Markdown shape changed, this is flagged as a breaking change above.
+- [ ] If a new runtime was added, a fixture under `examples/<runtime>-broken/` is included.
+
+## Test plan
+
+<!--
+What did you actually run? Include the exact commands and exit codes.
+Untested PRs may sit. Smoke against at least one example fixture.
+-->
+
+- [ ] Syntax check: `python3 -c "import py_compile; py_compile.compile('skills/pre-flight-check/scripts/run-pipeline.py', doraise=True)"`
+- [ ] `examples/node-broken/`: ran the pipeline, observed exit `1` + `### ❌ PRE-FLIGHT FAILURE: TYPECHECK`.
+- [ ] `examples/python-broken/`: ran the pipeline, observed exit `1` + `### ❌ PRE-FLIGHT FAILURE: TYPECHECK`.
+- [ ] Tested against a real project I work on (optional but encouraged — describe below).
+- [ ] CI is green.
+
+<details>
+<summary>Real-project smoke output (optional)</summary>
+
+```
+<paste output here>
+```
+
+</details>
+
+## SKILL.md impact
+
+- [ ] No change to agent contract.
+- [ ] Updated `SKILL.md` to reflect new behavior (describe below).
+
+## Docs
+
+- [ ] No user-visible change → no doc update needed.
+- [ ] `README.md` updated.
+- [ ] `INSTALL.md` updated.
+- [ ] `examples/README.md` updated.
+- [ ] N/A — docs-only PR.
+
+## Anything else reviewers should know
+
+<!-- Edge cases you noticed, tradeoffs you considered, follow-ups you'd like. -->