メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
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.
SOC 職業分類に基づく
| name | wp-status |
| description | 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. |
Give a short, accurate status of the FiberQ build plan and the per-task definition of done.
docs/private/, if present) and any project memory for the phase/version map (WP1→v1.3, WP2→v1.4, WP3→v1.5, WP4→v1.6; WP5 tests/CI is cross-cutting; WP6 docs ship per release).gh is available).fiberq/metadata.txt for the current plugin version.Keep it to a tight summary, not a wall of text.