菜单
Search across all cloned HMCTS repos using the workspace's pre-tuned ripgrep wrapper. Use when the user asks about code or text patterns spanning multiple service teams or platform components.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Summarise one HMCTS service's OpenAPI spec from cnp-api-docs. Reports title, version, auth, endpoint count by tag, owning product, hosted Swagger UI link, and local file path. Use when the user asks "what does pcs-api expose", "summarise ccd-data-store-api", "what auth does X use", "show me the endpoints of Y".
Find every product that uses a given CCD feature token (e.g. notice_of_change, case_flags). Use when the user asks "which services use X", "who has NoC enabled", "what products configure case flags".
Trace a CCD callback for a given event-id and service from definition through to controller. Returns the chain of file:line locations. Use when the user wants to know what runs when an event is submitted in a specific service.
Answer a "what is X" / "how does Y work" / "explain Z" question about any CFT topic — workspace, CCD, XUI, WA, AM, bulk-scan, platform/CNP. Routes via DOCS.md to the right page in either the root docs/ tree or a product-level apps/<product>/docs/ tree.
Find which HMCTS API service exposes a given HTTP path. Searches cnp-api-docs for matching OpenAPI paths and reports the owning service, methods, the local spec file, the hosted Swagger UI link and the workspace product that publishes it. Use when the user asks "which service has POST /cases/{id}/...", "what exposes /hearings", "where is /case-types defined", etc.
Find real, in-repo examples of how a feature is implemented in any HMCTS CFT product (CCD, XUI, WA, AM, bulk-scan, service teams). Use when the user wants concrete code references — "show me a real Notice of Change implementation", "where do they use case_flags", "give me an example of a mid-event callback".
基于 SOC 职业分类
| name | cft-cross-repo-search |
| description | Search across all cloned HMCTS repos using the workspace's pre-tuned ripgrep wrapper. Use when the user asks about code or text patterns spanning multiple service teams or platform components. |
The workspace has a tuned ripgrep wrapper at ./scripts/grep that excludes the noisy directories CFT projects accumulate (node_modules, build, .gradle, target, dist, .terraform, lock files, large generated jars). Always use it for workspace-spanning searches.
Use this skill when the user asks any of:
cd into the repo and use rg or Grep directly.INDEX.md via /cft-ccd-find-feature or /cft-list-integrations. Those are O(1); ripgrep is O(many GB)../scripts/grep '<pattern>'
./scripts/grep -t java '<pattern>' # ripgrep type filters work
./scripts/grep -l '<pattern>' # files only
./scripts/grep --glob '!**/test/**' '<pattern>' # additional excludes
The wrapper passes every flag through to rg and only adds the workspace's standard excludes plus the right search roots (apps libs platops).
Results are shown as path:line:match. Group by product (the segment after apps/) when summarising — the user usually cares about which products hit, not raw line counts.
For large result sets, prefer -l (file list) plus a follow-up read of the most relevant files over showing 100 raw match lines.