Skip to content

Conversation

@frankvegastudio
Copy link

@frankvegastudio frankvegastudio commented Oct 20, 2025

  • Added MCP-aware agent rules for Continue and GitHub integration
  • Streamlined agent mode to prioritize MCP tools (Filesystem, GitHub)
  • Enforced Conventional Commits, minimal diffs, and CI-first logic
  • Updated DEFAULT_SYSTEM_MESSAGES_URL to point to frank-vega-studio fork

Description

[ What changed? Feel free to be brief. ]

AI Code Review

  • Team members only: AI review runs automatically when PR is opened or marked ready for review
  • Team members can also trigger a review by commenting @continue-review

Checklist

  • [] I've read the contributing guide
  • [] The relevant docs, if any, have been updated or created
  • [] The relevant tests, if any, have been updated or created

Screen recording or screenshot

[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]

Tests

[ What tests were added or updated to ensure the changes work as expected? ]


Summary by cubic

Tightened system messages for chat, agent, and plan modes to prioritize MCP tools and CI/GitHub checks, enforce minimal diffs and Conventional Commits, and keep responses concise. Updated DEFAULT_SYSTEM_MESSAGES_URL to the frank-vega-studio raw source.

  • Refactors
    • Agent mode: prefer MCP Filesystem/GitHub; inspect CI status before edits; return minimal patches; avoid duplicate branches/PRs; preserve YAML formatting.
    • Standards: enforce Conventional Commits (feat, fix, chore, ci, docs, refactor, style, test).
    • Chat/Plan: chat answers stay brief and suggest Apply or Agent Mode; plan uses read-only tools and provides a short ordered plan before code suggestions.

- Added MCP-aware agent rules for Continue and GitHub integration
- Streamlined agent mode to prioritize MCP tools (Filesystem, GitHub)
- Enforced Conventional Commits, minimal diffs, and CI-first logic
- Updated DEFAULT_SYSTEM_MESSAGES_URL to point to frank-vega-studio fork
@frankvegastudio frankvegastudio requested a review from a team as a code owner October 20, 2025 18:24
@frankvegastudio frankvegastudio removed the request for review from a team October 20, 2025 18:24
@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Oct 20, 2025
@github-actions
Copy link

github-actions bot commented Oct 20, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 4 to 7
export const CODEBLOCK_FORMATTING_INSTRUCTIONS = `\
Always include the language and file name in the info string when you write code blocks.
If you are editing "src/main.py" for example, your code block should start with '\`\`\`python src/main.py'
If you are editing "src/main.py" for example, your code block should start with '```python src/main.py'
`;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 Badge Escape backticks in codeblock instructions to keep file parsable

The template literal defining CODEBLOCK_FORMATTING_INSTRUCTIONS now includes the example string '```python src/main.py' without escaping the backticks. Inside a template literal, raw backticks terminate the string, so this change makes defaultSystemMessages.ts fail to parse and will break any TypeScript build that touches this file. The previous revision used escaped backticks (\```) to avoid this. Re‑escape the backticks in the example so the source remains valid.

Useful? React with 👍 / 👎.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@frankvegastudio
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

- Restored DEFAULT_SYSTEM_MESSAGES_URL to upstream continuedev repo
- Escaped triple backticks in CODEBLOCK_FORMATTING_INSTRUCTIONS to keep file parsable
- Verified compliance with MCP/CI conventions
- Restored DEFAULT_SYSTEM_MESSAGES_URL to upstream continuedev repo
- Escaped triple backticks in CODEBLOCK_FORMATTING_INSTRUCTIONS to keep file parsable
- Verified compliance with MCP/CI conventions
frankvegastudio added a commit to frankvegastudio/continue that referenced this pull request Oct 20, 2025
Applies all diffs from PR continuedev#8351 including escaped backticks, tightened chat instructions, expanded agent principles, and corrected plan-mode guidance.
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@Patrick-Erichsen
Copy link
Collaborator

Patrick-Erichsen commented Oct 23, 2025

Thanks for the PR but the system message is quite sensitive so we'd prefer to not tweak at this time

@github-project-automation github-project-automation bot moved this from Todo to Done in Issues and PRs Oct 23, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Oct 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants