菜单
Updates the documentation in the currently open Markdown file based on Git changes. Use when: updating docs from PR changes, documenting all commits in a PR, syncing markdown documentation with local uncommitted edits or merged/open PR code changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generates sales-oriented feature descriptions from PR changes or attached files. Outputs a Slovak-language section describing the feature from a business/sales perspective with benefits, competitive advantages, and customer value. Use when: documenting a new feature for the sales team, generating sales descriptions from code changes, creating benefit lists for customer presentations.
Create WebJET CMS AppStore applications (page components) that appear in the editor application list and can be inserted into pages. Use when: creating new applications for the page editor, adding components to the AppStore, building page-insertable apps with @WebjetAppStore annotation, creating Spring MVC components with Thymeleaf views, adding application parameters with @DataTableColumn, configuring dynamic select options, or setting up multi-tab application editors.
Skill for writing E2E (end-to-end) tests using CodeceptJS with Playwright in WebJET CMS. Use when creating new automated browser tests, testing datatable CRUD operations, testing import functionality, verifying UI elements, testing permissions/rights, or writing test scenarios for admin pages.
Skill for programming WebJET CMS datatable backend - JPA entity, Spring DATA repository, REST controller, frontend HTML page, modinfo.properties and automated tests. Use when creating new admin CRUD applications, adding datatable entities, REST endpoints, or modifying existing datatable-based admin pages.
Translates code comments from Slovak to English without changing runtime behavior. Use when: code contains Slovak comments, reviewers request English-only comments, cleaning legacy comments before merge, standardizing documentation language in source files and tests.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
| name | wj-docs-pr |
| description | Updates the documentation in the currently open Markdown file based on Git changes. Use when: updating docs from PR changes, documenting all commits in a PR, syncing markdown documentation with local uncommitted edits or merged/open PR code changes. |
| argument-hint | Optionally specify which part of the documentation the changes apply to (e.g. "MetadataCleaner" or "page templates"). |
Analyzes Git changes and updates the content of the currently open Markdown document in Slovak.
Ask the user:
"Chcete zdokumentovať zmeny z celého pull requestu (všetky commity vetvy), alebo len necommitnuté lokálne zmeny?"
Based on the answer, use one of the two modes:
git rev-parse --abbrev-ref HEAD
git diff --name-only $(git merge-base HEAD origin/main)
For each file:
git diff $(git merge-base HEAD origin/main) -- <file>
git diff --name-only
git diff --cached --name-only
git status --short
For each file:
git diff <file>
git diff --cached <file>
Collect in both modes:
git rev-parse --abbrev-ref HEAD
Branch format: feature/XXXX-description or hotfix/XXXX-description — the ticket number is XXXX (digits between / and the first -).
For each relevant file (Java, JS, HTML templates, configuration) search for:
Read the entire contents of the currently open .md file to understand its structure and context.
Identify the sections that relate to the changed files (e.g. by class, module, function name).
Update the documentation directly in the open Markdown file:
Update types:
Open the file /docs/sk/CHANGELOG-2026.md and find the section ## 2026.0-SNAPSHOT. Add or append a record in the format:
- <brief description of the change in Slovak> (#XXXX)
where #XXXX is the ticket number from the branch name. If a record for this change already exists (without a ticket number), append (#XXXX) to the end of the line.
After the update, check:
(#XXXX)main, develop), omit the ticket number and notify the user.git rev-parse --abbrev-ref HEAD
git merge-base HEAD origin/main
Extract the ticket number from the branch name — format is feature/XXXX-description or hotfix/XXXX-description, the ticket number is XXXX (digits between / and the first -).
Compare the current branch against the merge-base (not against origin/main directly, to avoid including unrelated commits):
git diff --name-only $(git merge-base HEAD origin/main)
Collect:
A)M)D, R)For each relevant file (Java, JS, HTML templates, configuration) find what changed:
git diff $(git merge-base HEAD origin/main) -- <file>
Search for:
Read the entire contents of the currently open .md file to understand its structure and context.
Identify the sections that relate to the changed files (e.g. by class, module, function name).
Update the documentation directly in the open Markdown file:
Update types:
Find the ticket number from the name of the current git branch:
git rev-parse --abbrev-ref HEAD
The branch has the format feature/XXXX-description or hotfix/XXXX-description — the ticket number is XXXX (the digits between / and the first -).
Open the file /docs/sk/CHANGELOG-2026.md and find the section ## 2026.0-SNAPSHOT. Add or append a record in the format:
- <brief description of the change in Slovak> (#XXXX)
where #XXXX is the ticket number from the branch name. If a record for this change already exists (without a ticket number), append (#XXXX) to the end of the line.
After the update, check:
git diff $(git merge-base HEAD origin/main) are covered or intentionally omitted(#XXXX)main, develop), omit the ticket number and notify the user.wj-docs-uncommited, this skill covers all committed changes in the PR branch, not just local unstaged/staged edits.