Johnny Eric Amancio
75 lines
2.6 KiB
Markdown
75 lines
2.6 KiB
Markdown
## Issue
|
||
|
||
<!-- Reference an existing issue with `Fixes #123`, `Closes #123`, or equivalent linked issue wording. -->
|
||
|
||
Fixes #
|
||
|
||
## Context
|
||
|
||
<!-- Brief description of WHAT you’re doing and WHY. -->
|
||
|
||
## Implementation
|
||
|
||
<!--
|
||
|
||
Some description of HOW you achieved it. Perhaps give a high level description of the program flow. Did you need to refactor something? What tradeoffs did you take? Are there things in here which you’d particularly like people to pay close attention to? Keep this focused on context reviewers cannot infer from the diff; skip file-by-file summaries, placeholders, and other filler.
|
||
|
||
-->
|
||
|
||
## Screenshots / Video
|
||
|
||
<!-- Required for visual changes. Include the relevant before/after or resulting state. -->
|
||
|
||
| before | after |
|
||
|---|---|
|
||
| | |
|
||
|
||
## How to Test
|
||
|
||
### Manual/local verification
|
||
|
||
<!--
|
||
Describe local CLI, extension, or docs verification. Example:
|
||
- Opened the updated settings page and confirmed the new copy appears
|
||
-->
|
||
|
||
-
|
||
|
||
### Reviewer test steps
|
||
|
||
<!--
|
||
Provide steps reviewers can retrace. Example:
|
||
1. Sign in with a user with tracks
|
||
2. Activate `show_awesome_cat_gifs` feature by adding `?feature.show_awesome_cat_gifs=1` to your URL
|
||
3. Confirm you see a GIF with cats dancing
|
||
-->
|
||
|
||
-
|
||
|
||
### Blocked checks and substitute verification
|
||
|
||
<!--
|
||
If a relevant command could not be completed, name the command, explain the blocker or failure, and describe the substitute verification performed. Example:
|
||
- `bun run test:integration` could not complete because the required API key is unavailable; substitute verification was testing the affected flow manually in the development extension
|
||
-->
|
||
|
||
-
|
||
|
||
<!--
|
||
Every PR marked ready for review must include testing evidence. A bare "Not tested" or "N/A" answer is not sufficient. For each piece of evidence make clear if the test was executed by the agent or by a human
|
||
|
||
Docs-only, config-only, and similar changes still need concrete evidence. For examples, see [Testing Evidence for Pull Requests](https://kilo.ai/docs/contributing/development-environment#testing-evidence-for-pull-requests). Draft PRs may be incomplete until marked ready for review.
|
||
-->
|
||
|
||
## Checklist
|
||
|
||
- [ ] Issue linked above, or exception explained
|
||
- [ ] Tests/verification described
|
||
- [ ] Screenshots/video included for visual changes, or marked N/A
|
||
- [ ] Changeset considered for user-facing changes
|
||
- [ ] I personally reviewed the diff and can explain the changes, including any AI-assisted work.
|
||
|
||
## Get in Touch
|
||
|
||
<!-- We'd love to have a way to chat with you about your changes if necessary. If you're in the [Kilo Code Discord](https://kilo.ai/discord), please share your handle here. -->
|