This repository was archived by the owner on Aug 27, 2025. It is now read-only.
Workflow docs #58
Merged
Workflow docs #58
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chrarnoldus
requested review from
Copilot,
hassoncs,
kevinvandijk and
olearycrew
Contributor
There was a problem hiding this comment.
Pull Request Overview
Adds a new “Workflows” guide under slash-commands and updates the sidebar to surface it.
- Introduce
docs/features/slash-commands/workflows.mdxwith workflow usage, patterns, and an example. - Register the new page in
sidebars.ts.
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| sidebars.ts | Added 'features/slash-commands/workflows' to the sidebar |
| docs/features/slash-commands/workflows.mdx | Created detailed documentation for slash-command workflows |
Comments suppressed due to low confidence (3)
docs/features/slash-commands/workflows.mdx:6
- [nitpick] The placeholder syntax
/[workflow-name.md]could be confusing; consider updating to a clearer example like/my-workflow.mdor adding a note explaining that users should replace the bracketed text with their actual workflow filename.
Workflows automate repetitive tasks by defining step-by-step instructions for Kilo Code to execute. Invoke any workflow by typing `/[workflow-name.md]` in the chat.
docs/features/slash-commands/workflows.mdx:13
- [nitpick] Using
~to denote the home directory may be unclear to some users; consider specifying the full path convention (e.g.,$HOME/.kilocode/workflows/) or clarifying what~refers to.
- **Global workflows**: `~/.kilocode/workflows/` (available in all projects)
docs/features/slash-commands/workflows.mdx:58
- [nitpick] This example appears specific to a Cline developer's workflow; consider generalizing or replacing it with a more universally applicable example, or add a note indicating that it can be customized per team.
## Example: PR Submission Workflow
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Contributes to Kilo-Org/kilocode#531 and Kilo-Org/kilocode#578
Mostly copied from Cline docs. We probably want to either replace or remove the Real-world Example, because it seems very specific to a Cline developer's workflow.