You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit de270bd
Browse filesBrowse the repository at this point in the historyBrowse files
Update CI, docs and repo scripts for the genome split
The planner and genome checker pytest jobs (Node for check-genome.mjs),
the smoke and activation-gate scripts, the Studio Web flavor contract
test and the genome docs follow the new skill layout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .claude/commands/test-coverage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ Components are the specific, testable units the skill teaches. What counts as a
63
63
| RPA workflows (`uipath-rpa`) | Workflow modes (Coded C#, XAML), activity types, project types. Found in section headings like "Coded Workflows Quick Reference", "XAML Workflows Quick Reference". |
64
64
| Platform operations (`uipath-platform`) | CLI command groups (`uip orchestrator`, `uip is`), API domains. Found in "CLI Overview" command tables and Task Navigation. |
65
65
| Solution lifecycle (`uipath-solution`) |`uip solution` lifecycle (init, pack, publish, deploy, activate). Found in the CLI Surface Probe, Critical Rules, and Workflow sections of the SKILL.md. |
66
-
| Solution design + planning (`uipath-planner`) | PDD → SDD design (Phase D: PDD analysis, architecture review, SDD generation, product/scope selection, SDD templates) plus multi-skill task derivation (Lane A/B). Found in the Critical Rules, Entry Guard, Phase D, lane summaries, and Reference Navigation sections. |
66
+
| Solution design + planning (`uipath-planner`) | PDD → SDD design (`design`: PDD analysis, architecture review, SDD generation, product/scope selection, SDD templates) plus multi-skill task derivation (`plan`/`decompose`). Found in the Critical Rules, Choosing the Verb, the verb guides, and Reference Navigation sections. |
67
67
| Agent development (`uipath-agents`) | Lifecycle stages (Auth, Setup, Build, Bindings, Run, Deploy), framework types (LangGraph, LlamaIndex, etc.). Found in "Lifecycle Stages" section. |
68
68
| Coded apps (`uipath-coded-apps`) | Pipeline stages (Push, Pull, Pack, Publish, Deploy), app configuration concepts. Found in lifecycle and "Ship It" sections. |
69
69
| Cross-cutting capability (`uipath-context-grounding`) | The **modes × surfaces** matrix from the inventory doc: BatchTransform (coded, low-code), DeepRAG (coded, low-code), Index search (coded, low-code) — 6 components from `context-grounding-patterns.md` §The Three Modes + §Surface Selection. Found in the registered inventory source(s), NOT a SKILL.md. |
@@ -240,7 +240,7 @@ Count: `(Direct + Indirect) / Total`. Report Direct and Indirect separately in t
240
240
241
241
**Top untested buckets (roll-up signal).** After scoring components, record the **2–3 categories with the most `None` components** as a compact, comma-separated string — this is what makes the penalty legible from the SUMMARY without opening the per-skill file. Format each as `<category> <none>/<total>`, e.g. `triggers 0/3, IS connectors 0/2, run/publish 2/8`. Pick the categories that drag the score most (largest absolute `None` count; break ties by lowest coverage %). Rules:
242
242
- Derive these from the **same `None` rows** already in the Component Coverage tables — do not invent new groupings.
243
-
-**Planning skills (Components N/A)** and **catalog skills with no categories**: fall back to the largest-gap **workflow-step groups** or **rule groups** instead (e.g. `Lane A 0/10, entry-guard 0/1, rules 0/5`), so the column is never empty for a scored skill.
243
+
-**Planning skills (Components N/A)** and **catalog skills with no categories**: fall back to the largest-gap **workflow-step groups** or **rule groups** instead (e.g. `plan`0/10, verb-choice 0/1, rules 0/5), so the column is never empty for a scored skill.
244
244
-**Skills with no tests / planned skills:** use `all (no tests)` / `— (planned)` respectively.
245
245
- Keep it under ~60 chars; it rides in one Overview cell. The full enumeration stays in the per-skill report's **Untested Features** section — this is just the headline.
0 commit comments