Creating a Review document with save to project option
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the feature or problem you'd like to solve
Similar to the /research (-> 'report') and /plan (-> 'plan') slash commands executing /review should also generate a standard output document.
### Proposed solution
Would provide a harmonized behavior for all three agents and a useful output for the /review command.
### Example prompts or workflows
```/review the spec @my_spec``` should result in an output document e.g. named "Review.md".
Similar for review code snippets or (implementation) plans.
### Additional context
_No response_
Contributor guide
Research direction
Start by comparing how the /research and /plan slash commands generate and save their standard output documents. Implement matching behavior for /review, including the example spec, code-snippet, and implementation-plan workflows, and verify that the result is saved as a document named Review.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100