菜单
Use when a synced FineReport change must be opened in browser and checked against the expected data and layout, especially when preview URLs, login flow, and browser evidence should follow a fixed FineReport review routine instead of rediscovering the page each time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when editing FineReport `.cpt` files after the datasource, target path, and creation or pull prerequisites are clear. Trigger for CPT layout, dataset XML, parameters, table headers, and cell-level report edits.
Use when a new FineReport CPT or FVS file must be created, when same-name collisions must be checked before writing, or when a template must be selected before local editing begins.
Use when FineReport datasource connections, SQL previews, field scans, or dataset XML snippets are needed before editing CPT or FVS files. Trigger whenever the request involves connection names, columns, parameters, or data validation.
Use when a remote reportlet must be pulled into the local project before comparison or editing. Trigger whenever the latest remote CPT or FVS content is required as the editing baseline.
Use when editing FineReport `.fvs` files after datasource, target path, and creation or pull prerequisites are clear. Trigger for FVS tree structure, view definitions, and grouping or aggregation changes.
Use when starting or reinitializing a FineReport project and `.codex/fr-config.json` is missing, incomplete, stale, or the user explicitly asks to regenerate the project config.
| name | fr-browser-review |
| description | Use when a synced FineReport change must be opened in browser and checked against the expected data and layout, especially when preview URLs, login flow, and browser evidence should follow a fixed FineReport review routine instead of rediscovering the page each time. |
Use this skill to run the last browser-review step with a fixed FineReport routine. It assumes the page will be driven by the repo-local .codex/skills/chrome-devtools/ skill, which wraps the official ChromeDevTools/chrome-devtools-mcp server, and that login, page open, and review targets come from project config plus the current task context.
Preferred browser skill:
chrome-devtools.codex/skills/chrome-devtools/ChromeDevTools/chrome-devtools-mcp.codex/skills/chrome-devtools/references/setup-and-tools.mdDo not switch to another browser skill unless the user explicitly asks.
.codex/fr-config.jsonreportlets/... path that can derive onereportlets/demo/report.cptpython3 .codex/skills/fr-browser-review/scripts/run.py --config-path .codex/fr-config.json --url <预览地址> --report-path reportlets/<目标文件> --expectation "<复核重点>" --queriedpy .codex\\skills\\fr-browser-review\\scripts\\run.py --config-path .codex\\fr-config.json --url <预览地址> --report-path reportlets\\<目标文件> --expectation "<复核重点>" --queriedPreview URL rules:
.cpt: /webroot/decision/view/report?viewlet=<reportlets/之后的路径>.fvs: /webroot/decision/view/duchamp?page_number=1&viewlet=<reportlets/之后的路径>--url is omitted but --config-path and --report-path are present, the wrapper derives the canonical preview URL from these ruleschrome-devtools with this exact order:decision_url from .codex/fr-config.jsonusername and password from .codex/fr-config.jsondecision_url from .codex/fr-config.jsonusername and password from .codex/fr-config.json.fvs, always use the view/duchamp?page_number=1&viewlet=... route instead of view/reportSee references/browser-review-playbook.md for the exact review routine.
EXAMPLES.md
references/browser-review-playbook.md
references/review-template.md
.codex/fr-config.json is missingchrome-devtools MCP server is unavailable