PR type
Weave uses an AI agent to categorize every PR into one of the following types:Feature
A feature PR introduces new functionality or innovation.Examples
Examples
- Adding a new user dashboard
- Implementing a new search algorithm
- Creating a new API endpoint
- Adding a new report type
Bug
A “bug” PR fixes something that is broken or not working as intended.Examples
Examples
- Fixing a login issue reported by users
- Addressing a security vulnerability
- Correcting a calculation error
- Fixing a UI element that’s not displaying correctly
KTLO (keeping the lights on)
KTLO PRs represent maintenance work that keeps the system running but doesn’t introduce new functionality. Anything that’s not a feature or a bug is categorized as KTLO.Examples
Examples
- Refactoring a module for better maintainability
- Improving database query performance
- Updating documentation
- Adding new tests
- Moving code between repositories
- Deploying to new environments
- Making debugging tools more accessible
Component categories
Weave also labels each PR by the area of the codebase it touches, based on the files changed and the PR description. Every organization starts with three built-in components: frontend, backend, and infrastructure. You can add custom components — such asmobile or database — under Code components in Settings. Custom components take priority over the defaults, and you can add a description to help Weave assign them more accurately. Weave will also suggest components based on your 20 most recent PRs.
Custom components apply to PRs merged on or after the component is added, even if the PR was opened earlier. PRs merged before the component was added are not relabeled when a custom component is created.
Improving type categorization
The PR type categorization is smart but it’s not perfect. To improve its accuracy, you can manually override the categorization. To do so, click on the PR type and select the correct category:
Over time, Weave will learn from your overrides and improve its categorization accuracy.