Skip to content

feat: automated Benchmark Context Architect daily sync#378

Open
beginwebdev2002 wants to merge 1 commit into
mainfrom
benchmark-context-architect-17914160742267111291
Open

feat: automated Benchmark Context Architect daily sync#378
beginwebdev2002 wants to merge 1 commit into
mainfrom
benchmark-context-architect-17914160742267111291

Conversation

@beginwebdev2002
Copy link
Copy Markdown
Owner

Implements the "Benchmark Context Architect" process as requested.

The process requires a daily job to scan for updated or untracked .md files in frontend/backend, sync golden prompts/AST rules using TS-Morph and Google GenAI, and conditionally either auto-commit or open an issue based on the fidelity score.

  • Created .github/workflows/benchmark-sync.yml to trigger the node vibe-check-runner.js script daily at 02:00 AM.
  • Granted write permissions to the action for contents and issues.
  • Updated vibe-check-runner.js to correctly incorporate untracked files into the CI/CD scan step (git ls-files).
  • Fixed a bug in vibe-check-runner.js that would overwrite temporary AST files when scanning multiple files of the same technology.

PR created automatically by Jules for task 17914160742267111291 started by @beginwebdev2002

…ions

- Added a daily GitHub Action (`.github/workflows/benchmark-sync.yml`) to run the vibe-check-runner at 02:00 AM.
- Granted 'contents: write' and 'issues: write' permissions so the action can auto-commit valid AI benchmarks to `main` with `[chore: benchmark-sync]` or open critical issues on failure.
- Updated `vibe-check-runner.js` to also capture untracked files using `git ls-files -m -o --exclude-standard`.
- Fixed `vibe-check-runner.js` iteration to generate dynamic temporary TypeScript files (`temp_${tech}_${file.replace(/\//g, '_')}.ts`) to prevent AST processing state collisions.

Co-authored-by: beginwebdev2002 <102213457+beginwebdev2002@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant