Maintainer of this skill?
by feiskyer
Automated pull requests reviewing and issues triaging with ChatGPT.
# Add to your Claude Code skills
git clone https://github.com/feiskyer/ChatGPT-ReviewerGuides for using ai agents skills like ChatGPT-Reviewer.
See how ChatGPT-Reviewer compares with popular alternatives.
ChatGPT-Reviewer is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by feiskyer. Automated pull requests reviewing and issues triaging with ChatGPT. It has 100 GitHub stars.
ChatGPT-Reviewer's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/feiskyer/ChatGPT-Reviewer" and add it to your Claude Code skills directory (see the Installation section above).
ChatGPT-Reviewer is primarily written in Python. It is open-source under feiskyer on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ChatGPT-Reviewer against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Automated pull requests reviewing and issues triaging with ChatGPT.
Create an OpenAI API key here, and then set the key as an action secret in your repository named OPENAI_API_KEY.
Finally, create a file named .github/workflows/chatgpt-review.yml with the following contents:
name: ChatGPT Review
on: [pull_request]
jobs:
chatgpt-review:
name: ChatGPT Review
runs-on: ubuntu-latest
steps:
- uses: feiskyer/ChatGPT-Reviewer@v0
name: ChatGPT Review
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
# OPENAI_API_BASE: ${{ secrets.OPENAI_API_BASE }}
# Optional configurations:
# with:
# model: "gpt-3.5-turbo"
# temperature: 0.2
# review_per_file: true
# comment_per_file: true
| Parameter | Description | Required | Default |
|---|---|---|---|
| GITHUB_TOKEN | Github token used to send out review comments | true | "" |
| OPENAI_API_KEY | API key used to invoke OpenAI | true | "" |
| OPENAI_API_BASE | API based used to access Azure OpenAI | false | "" |
| blocking | Blocking the pull requests on OpenAI failures | false | False |
| model | OpenAI model name | false | gpt-3.5-turbo |
| temperature | Temperature for the model | false | 0.2 |
| frequency_penalty | Frequency penalty for the model | false | 0 |
| presence_penalty | Presence penalty for the model | false | 0 |
| review_per_file | Send out review requests per file | false | Large changes would be reviewed per file automatically |
| comment_per_file | Post review comments per file | false | True |
The ChatGPT reviewer PRs are also getting reviewed by ChatGPT, refer the pull requests for the sample review comments.
In order to protect public repositories for malicious users, Github runs all pull request workflows raised from repository forks with a read-only token and no access to secrets.
pull_request_target event could be used in such cases, which would run the workflow in the context of the base of the pull request (rather than in the context of the merge commit, as the pull_request event does).
Refer Github docs here for more details of pull_request_target event.