Skip to content

Add Python prompt exports for system and backend prompts#41

Open
justinlietz93 wants to merge 1 commit into
mainfrom
codex/extract-prompts-into-separate-python-files
Open

Add Python prompt exports for system and backend prompts#41
justinlietz93 wants to merge 1 commit into
mainfrom
codex/extract-prompts-into-separate-python-files

Conversation

@justinlietz93

Copy link
Copy Markdown
Owner

Summary

  • add python prompt export files for all system prompt modules with multi-line string definitions
  • capture backend planning, critique, and recovery prompts as dedicated python modules for reuse

Testing

  • npm run lint
  • npm run format

https://chatgpt.com/codex/tasks/task_e_68dc2bf9e638832690dafad254d95a7e

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sorry @justinlietz93, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@github-actions

Copy link
Copy Markdown

Coverage Report

Extension Coverage

Base branch: 0%

PR branch: 0%

✅ Coverage increased or remained the same

Webview Coverage

Base branch: 0%

PR branch: 0%

✅ Coverage increased or remained the same

Overall Assessment

Test coverage has been maintained or improved

Last updated: 2025-09-30T23:46:03.414020

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

Copy link
Copy Markdown

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

Comment on lines +41 to +46
├── package.json
{
...
"type": "module", // added by default, uses ES module syntax (import/export) rather than CommonJS (require/module.exports) (Important to know if you create additional scripts in this server repository like a get-refresh-token.js script)
"scripts": {
"build": "tsc && node -e \"require('fs').chmodSync('build/index.js', '755')\"",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Escape braces in mcp_prompt format string

The mcp_prompt text includes placeholders ({connected_server_details}, {mcp_servers_path}) which implies it will be interpolated via str.format(...). The embedded TypeScript example also contains literal JSON braces like { "type": "module" } and a nested "scripts": { … } block. Because those braces aren’t escaped ({{/}}), formatting the prompt will raise KeyError for names such as type or scripts, making the prompt unusable whenever dynamic values are inserted. These braces need to be escaped or the interpolation strategy changed.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant