fix(skills): enhance solution editing guidance and durable gotchas#501
Merged
Conversation
Improvements surfaced through end-to-end testing of multi-project solution authoring (RPA + Python agent + Maestro Flow + Maestro Case + Tests): - uipath-platform/develop-solution.md: new "Field-tested gotchas" section (state verification, bindings.json vs bindings_v2.json schemas, stderr- checked refresh for false-success on schema errors, orphan package resources after project remove); document --solution-folder flag migration on resource list/refresh; transactional add note; three-name divergence on import; empty-target solution new behavior. - uipath-platform/solution.md: expanded file structure with annotations; note that coded apps are not registered in .uipx. - uipath-platform/pack-and-deploy.md: add solution-state verification to prerequisites; remove transitory "currently broken" bug mention. - uipath-agents/setup.md: recommend packOptions.directoriesExcluded for .venv and __pycache__ when the agent project is part of a solution upload. - uipath-rpa/coded-vs-xaml-guide.md: clarify that uip rpa create-project is mode-agnostic; coded vs XAML is decided per-workflow. - uipath-maestro-case/case-commands.md: document uip maestro case init as a first-class scaffold command (counterpart to uip maestro flow init). - uipath-coded-apps/SKILL.md: note coded apps are not .uipx-registered; they deploy independently via uip codedapp publish/deploy. - Bump plugin version 0.0.21 → 0.0.22. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Consider adding smoke tests before merging. |
gabrielavaduva
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improvements surfaced through end-to-end testing of multi-project solution authoring (RPA + Python agent + Maestro Flow + Maestro Case + Tests). Adds durable CLI gotchas, documents API migrations, and removes transitory bug references.
Changes
uipath-platform
develop-solution.md: new "Field-tested gotchas" section — state verification after every mutation,bindings.jsonvsbindings_v2.jsonschema distinction, stderr-checked refresh for false-success on schema errors, orphan package resources afterproject remove. Documents--solution-folderflag migration onresource list/refresh. Transactionaladdnote. Three-name divergence onimport. Empty-targetsolution newbehavior.solution.md: expanded file structure with inline annotations; note that coded apps are not registered in.uipx.pack-and-deploy.md: solution-state verification added to prerequisites; transitory "currently broken" bug mention removed.uipath-agents
lifecycle/setup.md: recommendpackOptions.directoriesExcluded: [".venv", "__pycache__"]when an agent project is part of a solution upload (avoids huge archives and Studio Web rejection).uipath-rpa
coded-vs-xaml-guide.md: clarify thatuip rpa create-projectis mode-agnostic; coded vs XAML is decided per-workflow, not at project creation. There is no--codedflag.uipath-maestro-case
case-commands.md: documentuip maestro case init <name>as a first-class scaffold command (counterpart touip maestro flow init), separate from the SDD-driven JSON authoring path.uipath-coded-apps
SKILL.md: note that coded apps are not.uipx-registered (noproject.uiproj/project.json); they deploy independently viauip codedapp publish/deploy.Plugin manifest
0.0.21→0.0.22.Test plan
develop-solution.md; verify state checks pass andresource refreshstderr capture works as documentedcoded-vs-xaml-guide.mdflowchart still parses cleanly with the new lead-in sectionuip maestro case initexample command incase-commands.md🤖 Generated with Claude Code