docs(dify-plugin): document the full tool set added by the port#31
Conversation
There was a problem hiding this comment.
1 issue found across 4 files
You’re at about 98% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/dify-plugin/README.md">
<violation number="1" location="apps/dify-plugin/README.md:45">
P3: This suggests **Run Code** can build or launch the cloned project, although it only executes a supplied snippet and cannot select the repository as an entrypoint or working directory. Document **Run Command** for project build/run steps, and reserve **Run Code** for snippets that interact with the checkout.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
You’re at about 99% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
The plugin registers 17 tools but the README/metadata only described the original 7. Document the 10 added tools (list_sandboxes, manage_sandbox, git_clone, read_file, write_file, list_files, search_files, find_in_files, start_service, get_service_logs): - README: add them to Features and the Tool Reference table, plus usage sections for git, services/preview, files, and sandbox management - manifest.yaml + provider: broaden the plugin description beyond 'run code and commands' - PRIVACY.md: cover Write/Read File transfers and Git Clone credential handling Signed-off-by: Mislav Ivanda <mislavivanda454@gmail.com>
cubic review: the git-repo usage section implied Run Code could build/launch the project, but Run Code only executes a supplied snippet (no cwd/entrypoint). Point build/run steps at Run Command (with cwd) and describe Run Code as running snippets against the checkout. Signed-off-by: Mislav Ivanda <mislavivanda454@gmail.com>
…un Command cubic review: 'start the app' under Run Command could lead to a foreground command that blocks/times out (Run Command is synchronous). Limit Run Command examples to finite build/test steps and defer server startup to Start Service. Signed-off-by: Mislav Ivanda <mislavivanda454@gmail.com>
83d40e9 to
389c2f8
Compare
|
All contributors have signed the CLA. ✅ Thank you! |
|
I have read the CLA Document and I hereby sign the CLA |
Summary by cubic
Document the full Daytona Dify plugin toolset and align metadata with its capabilities.
README lists all 17 tools and clarifies Git, files, services, and sandbox management (build/test via Run Command + cwd; snippets/charts via Run Code; long‑running via Start Service + Preview/Logs); PRIVACY covers Read/Write File and Git Clone credentials (not retained); manifest/provider descriptions are broadened.
Written for commit 389c2f8. Summary will update on new commits.