Skip to content

Feat: AI review integration on Github - #218

Draft
ThomasB-Colibri wants to merge 2 commits into
devfrom
feat-ai-integration
Draft

Feat: AI review integration on Github#218
ThomasB-Colibri wants to merge 2 commits into
devfrom
feat-ai-integration

Conversation

@ThomasB-Colibri

Copy link
Copy Markdown
Collaborator

No description provided.

@github-actions github-actions Bot added maintenance enhancement New feature or request AI labels Sep 2, 2026
@ThomasB-Colibri ThomasB-Colibri changed the title feat: add AI tag to PR's Feat: AI integration on Github Sep 2, 2026
@hJaffaliColibritd hJaffaliColibritd changed the title Feat: AI integration on Github Feat: AI review integration on Github Sep 10, 2026
Comment thread AGENTS.md

Start by understanding the pull request's stated goal and its complete diff against
the merge base. Review changed behavior in context: inspect callers, sibling
implementations, tests, public exports, and documentation. Do not report unrelated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

add requirements ?

Comment thread AGENTS.md
## Review objective

Review MPQP as a user-facing scientific library and as a provider-independent
abstraction over several quantum SDKs. Prioritize observable correctness,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

"observable correctness" is confusing, clarify or just keep "correctness of the result " ?

Comment thread AGENTS.md
not for implementing a change. Do not modify the pull request unless the user asks
for fixes explicitly.

## Review objective

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe add performing local tests, (or adding tests and running them?), to check correct resutls and behavior from user point of view, and no error / bug / performance problems introduced

Comment thread AGENTS.md

Start by understanding the pull request's stated goal and its complete diff against
the merge base. Review changed behavior in context: inspect callers, sibling
implementations, tests, public exports, and documentation. Do not report unrelated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

clarify what is "public exports"

Comment thread AGENTS.md
not for implementing a change. Do not modify the pull request unless the user asks
for fixes explicitly.

## Review objective

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Don't know where to put it, but for small fixes and syntax, or small mistakes, put directly a suggestion of change in the comment of the commit (so the user can directly accept or not the change, but the AI don't act and don't modify)

Comment thread AGENTS.md
- shared mutable defaults such as `[]` or `{}`;
- shallow copies presented as deep copies, or redundant `deepcopy` calls;
- one instruction reused in multiple positions or circuits;
- stale cached environment/provider state;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

clarify this point, not clear

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

Labels

AI enhancement New feature or request maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants