wp-status

Étoiles22

Forks6

Mis à jour29 juin 2026 à 18:40

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

vukovicvl

vukovicvl/fiberq

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

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.

How

Read the build plan (the planning doc under 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).
Check git state: current branch, latest tag, recent commits, and open PRs (if gh is available).
Read fiberq/metadata.txt for the current plugin version.

Report

Current plugin version and what's released.
Which WP/phase is in progress and what is left in it.
The next task and its definition of done:
- feature branch merged to main,
- tagged release with a changelog entry,
- tests added/updated and green in CI,
- docs/spec/demo published and linkable,
- the deliverable is the new increment (not pre-existing code).
Any blockers or decisions waiting on the maintainer.

Keep it to a tight summary, not a wall of text.

Plus depuis ce dépôt

même dépôt

scan-check

vukovicvl/fiberq

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.

2026-07-1422

green

vukovicvl/fiberq

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.

2026-06-2922

prepublish

vukovicvl/fiberq

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.

2026-06-2922

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.

How

Read the build plan (the planning doc under 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).
Check git state: current branch, latest tag, recent commits, and open PRs (if gh is available).
Read fiberq/metadata.txt for the current plugin version.

Report

Current plugin version and what's released.
Which WP/phase is in progress and what is left in it.
The next task and its definition of done:
- feature branch merged to main,
- tagged release with a changelog entry,
- tests added/updated and green in CI,
- docs/spec/demo published and linkable,
- the deliverable is the new increment (not pre-existing code).
Any blockers or decisions waiting on the maintainer.

Keep it to a tight summary, not a wall of text.