Restrict Gemini/Cursor/Kiro engines to smoke-* workflows - #51869
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Moves daily automation from limited-credit Cursor/Kiro engines to Copilot while retaining those engines for smoke tests only.
Changes:
- Switched four daily workflows to Copilot SDK.
- Removed engine-specific imports and wording.
- Regenerated corresponding compiled workflows.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/daily-pr-review-cursor.md |
Migrates PR review to Copilot. |
.github/workflows/daily-pr-review-cursor.lock.yml |
Regenerates compiled PR review workflow. |
.github/workflows/daily-schema-audit-cursor.md |
Migrates schema audit to Copilot. |
.github/workflows/daily-schema-audit-cursor.lock.yml |
Regenerates compiled schema audit workflow. |
.github/workflows/daily-regression-audit-kiro.md |
Migrates regression audit to Copilot. |
.github/workflows/daily-regression-audit-kiro.lock.yml |
Regenerates compiled regression audit workflow. |
.github/workflows/daily-spec-coverage-kiro.md |
Migrates specification coverage review to Copilot. |
.github/workflows/daily-spec-coverage-kiro.lock.yml |
Regenerates compiled specification review workflow. |
Review details
Tip
Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 6/8 changed files
- Comments generated: 0
- Review effort level: Balanced
Copilot created this pull request from a session on behalf of
pelikhan
August 10, 2026 20:53
View session
Contributor
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gemini, Cursor, and Kiro have limited credits and should only be exercised in smoke-test workflows, not in daily production automation.
Findings
geminiengine — onlysmoke-gemini.mddid.daily-*workflows usedcursor/kiro, burning through their credits on a schedule.Changes
daily-pr-review-cursor.md,daily-schema-audit-cursor.md— engine switched fromcursortocopilot(copilot-sdk: true); droppedshared/cursor.mdimport and "using Cursor" wording.daily-regression-audit-kiro.md,daily-spec-coverage-kiro.md— engine switched fromkirotocopilot(copilot-sdk: true); droppedshared/kiro.mdimport and "using Kiro" wording..lock.ymlfor all four workflows.smoke-cursor.md,smoke-kiro.md,smoke-gemini.mdleft untouched — these remain the sanctioned place to run these engines.