メニュー
Fetch a Koha Bugzilla bug's summary, description, status, and recent comments from bugs.koha-community.org by bug number. Use before starting work on a bug to surface the test plan and any prior discussion. Argument: a Koha bug number (e.g. 33501).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
File a Koha bug on bugs.koha-community.org and attach commits non-interactively via git bz. Use when the user wants to submit a patch, file a bug, or open a bz/Bugzilla ticket for Koha. Arguments (optional, free-form): summary or component hints. Without args, derive details from the current branch and HEAD commits.
Build Koha frontend assets (CSS, JS, OpenAPI spec) inside the KTD container. Use after editing SCSS, Vue components, or api/v1/swagger/*.yaml. After swagger changes you must also run restart_all to reload services — yarn build alone is not enough.
Run Koha Cypress end-to-end tests. Cypress runs from the HOST (not the KTD container) — KTD exposes the staff/OPAC interfaces on localhost and Cypress drives a real browser. Pass a spec path or directory under t/cypress/integration/.
Run Koha Perl tests inside the KTD container. Pass a test file or directory path (relative to the Koha repo root, or absolute). Handles both t/ and t/db_dependent/ automatically.
Run the Koha QA script (koha-qa.pl) inside KTD before submitting patches. Surfaces critic, POD, file_permissions, tinyint_has_boolean_flag, and other QA failures the community reviewers will check. Run after every commit; fix flagged issues before pushing.
Apply a Koha DB schema change end-to-end after editing kohastructure.sql and the atomicupdate file. Runs updatedatabase.pl in KTD, regenerates DBIC schema with dbic --force, and reminds about the manual is_boolean / relationship edits below the marker line. Use this after the atomicupdate skill has scaffolded the file and the SQL is filled in.
| name | koha-bz-fetch |
| description | Fetch a Koha Bugzilla bug's summary, description, status, and recent comments from bugs.koha-community.org by bug number. Use before starting work on a bug to surface the test plan and any prior discussion. Argument: a Koha bug number (e.g. 33501). |
Fetch a Koha Bugzilla bug by number.
Arguments: $ARGUMENTS — a single bug number (e.g. 33501).
Validate the argument is a positive integer. If the user passed a URL like
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=NNNNN, extract
the number from the id parameter.
If git bz is configured (~/.git-bz exists), use it:
git bz show NNNNN
This dumps the bug header, full description, and recent comments to stdout using the user's authenticated session — works for restricted bugs too.
curl -sf "https://bugs.koha-community.org/bugzilla3/rest/bug/NNNNN" \
| jq '.bugs[0] | {id, summary, status, resolution, severity, component, version, assigned_to, creator, creation_time, last_change_time}'
For comments:
curl -sf "https://bugs.koha-community.org/bugzilla3/rest/bug/NNNNN/comment" \
| jq '.bugs["NNNNN"].comments[] | {id: .count, who: .creator, when: .creation_time, text: .text}'
(Substitute NNNNN literally in the jq path — Bugzilla keys comments by
the bug id as a string.)
Direct link to share with the user:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=NNNNN
Summarise the bug in 5–10 lines:
<summary> ([status, severity, component])Test plan: if present
in the description.End with the bug URL. Don't dump the full comment thread — surface what matters for starting work.
git bz is configured.