-
Notifications
You must be signed in to change notification settings - Fork 3.2k
feat: generate rule dialog #6421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for continuedev canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cubic found 7 issues across 19 files. Review them in cubic.dev
React with 👍 or 👎 to teach cubic. Tag @cubic-dev-ai
to give specific feedback.
3c7cc87
to
e2a7d47
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- alwaysApply could be confusing for the model (didn't we remove before because of this?). Instead, we could map the user-friendly names like agent requested to the tool args somehow
- Button borders have looked a bit clanky, should we fix since this form has many?
- the new llmStreamChat with tools adds surface area in a way that might be hard to work with in the future, e.g. won't work with virtual tools. We should combine into util
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only show for native tool support models
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should add the continue.generateRule command for jetbrains
@@ -13,7 +13,7 @@ export const createRuleBlock: Tool = { | |||
function: { | |||
name: BuiltInToolNames.CreateRuleBlock, | |||
description: | |||
'Creates a "rule" that can be referenced in future conversations. This should be used whenever you want to establish code standards / preferences that should be applied consistently, or when you want to avoid making a mistake again. To modify existing rules, use the edit tool instead.', | |||
'Creates a "rule" that can be referenced in future conversations. This should be used whenever you want to establish code standards / preferences that should be applied consistently, or when you want to avoid making a mistake again. To modify existing rules, use the edit tool instead.\n\nRule Types:\n- Always: Include only "rule" (always included in model context)\n- Auto Attached: Include "rule", "globs", and/or "regex" (included when files match patterns)\n- Agent Requested: Include "rule" and "description" (AI decides when to apply based on description)\n- Manual: Include only "rule" (only included when explicitly mentioned using @ruleName)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change alwaysApply to a more readable "rule_type" arg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Patrick-Erichsen saving this change for later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nvm saw your comment
|
||
export const createRuleBlockImpl: ToolImpl = async ( | ||
args: CreateRuleBlockArgs, | ||
{ name, rule, ...otherArgs }: CreateRuleBlockArgs, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the advantage over saying otherArgs
syntax vs just saying { name, rule, description }
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hahaha it had a good run
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Screenshots
Summary by cubic
Added a "Generate rule" button and dialog that lets users create new coding rules from chat history, with support for different rule types and streaming rule generation.