The repository improvements surface finds practical work when a codebase needs attention and the starting point is unclear. Generate suggestions, keep the useful ones, then save them as todos or open a plan.
Select a health or growth category, or add custom instructions when the analysis should focus on a specific goal.
Focus on test coverage and error handling in the payments module. Prioritize changes that reduce flaky integration tests, and skip pure style or formatting suggestions.
Pick the agent and model that fit the repository size and the quality bar for the suggestion pass.
Use another repository as an example when the target should follow patterns from a sibling project.
Keep the suggestions that are specific enough to implement and discard generic or low-value items.
Save selected suggestions to repository todos when they need triage, or open a planning draft when they are ready for implementation.
Improvement suggestions provide the generation controls; a selected suggestion moves straight into a plan or waits until related todos are ready to be implemented together.