メニュー
Fetch a Confluence page's details (title, space, version, labels, body HTML) by page ID or URL. Use whenever another skill or task needs to read a Confluence page.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | read-confluence-page |
| description | Fetch a Confluence page's details (title, space, version, labels, body HTML) by page ID or URL. Use whenever another skill or task needs to read a Confluence page. |
args is a space-separated string: <page_id_or_url> [format]
123456789) or full page URL (e.g. https://eaflood.atlassian.net/wiki/spaces/FOO/pages/123456789/Title).full (default), summary, or json.Run the page script:
bash ./.ai/skills/tools/confluence/page.sh <page_id_or_url> [format]
Requires ATLASSIAN_USER and ATLASSIAN_TOKEN env vars. See atlassian-credentials.md for setup.
If the script fails for any reason, stop immediately. Report the exact error to the user and ask them to fix it before retrying. Do not fall back to scraping the Confluence UI or guessing the page contents.
Return the script's output to the caller. Do not summarise or filter — the caller needs the full page details to do its job.
Fetch a Jira ticket's details (summary, description, acceptance criteria, testing notes) by ticket ID. Use whenever another skill or task needs to read a Jira ticket.
Create a new page and associated files by parsing a prototype page
Test a page in the browser against accessibility standards.
Conventions and file structure for quote journey pages in nrf-frontend. Read before creating or modifying any page under frontend/src/server/quote/. Covers the standard file structure (routes, get-view-model, form-validation, get-next-page), quoteController / quotePostController wiring, PRG validation flow, Nunjucks template conventions, Joi rules per input type, session cache helpers, and page/accessibility test patterns.
Reviews changed code against team coding standards. Use after writing code in a nrf-* repository
Audit and fix the @openapi JSDoc annotations across all API route and controller files in frontend/ and backend/ so the Swagger documentation matches the actual endpoint implementations. Run for one or both sub-repos.