メニュー
Run the FiberQ pre-publish checklist for a release (version sync, changelog, scan-clean, tests green, package builds, GenAI disclosure, secrets, manual-test reminder). Use right before tagging/publishing a version. Reports a readiness status; never pushes or uploads.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Predict the plugins.qgis.org Security & Quality scan locally (flake8 + Bandit), no Docker needed. Use before any upload/release, or after a change, to confirm the plugin still scans with zero findings.
Run the FiberQ lint+test gate inside the official QGIS Docker images (the same thing CI runs) and report pass/fail per image. Use to make the build green locally before pushing or opening a PR. Requires Docker.
Summarise where the FiberQ build is — current work package / phase, what's done, what's next, and the per-task definition of done. Use to orient at the start of a session or before starting a new task.
| name | prepublish |
| description | Run the FiberQ pre-publish checklist for a release (version sync, changelog, scan-clean, tests green, package builds, GenAI disclosure, secrets, manual-test reminder). Use right before tagging/publishing a version. Reports a readiness status; never pushes or uploads. |
Walk the release checklist and report status for each item. Do NOT push, tag, or upload — this is a readiness check only.
version= in fiberq/metadata.txt equals __version__ in fiberq/__init__.py (the smoke test enforces this).changelog= in fiberq/metadata.txt has an entry for this version.scan-check gate: flake8 0 + Bandit medium/high 0.green passes on both QGIS images (or CI is green on the pushed commit).make package produces dist/fiberq-<version>.zip; verify a single top-level fiberq/, that it includes metadata.txt/__init__.py, and that it contains no __pycache__ and no dev/hidden files.fiberq/README.md (shipped) and the repo-root README.md (public landing page).fiberq/config.ini has placeholders only; no credentials anywhere in the diff.A pass/fail table, then the remaining manual steps (push, tag, upload to plugins.qgis.org, publish docs) listed for the maintainer — never execute them here.