MCP.so
登录

PR Intent Checker GitHub Action (MCP Server Packaged)

@kevinjcwu

基本信息

分类

版本控制

传输方式

stdio

作者

kevinjcwu

关于 PR Intent Checker GitHub Action

PR Intent Checker action with packaged MCP server

PR Intent Checker GitHub Action 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

PR Intent Checker GitHub Action 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is PR Intent Checker GitHub Action (MCP Server Packaged)?

A GitHub Action that uses Azure OpenAI to analyze a PR’s code changes against requirements in a linked GitHub Issue, detecting intent drift. It packages the GitHub MCP server inside the Docker container to interact with the GitHub API.

How to use PR Intent Checker GitHub Action (MCP Server Packaged)?

Add the action to a workflow with the required permissions and inputs (github_token, azure_openai_endpoint, azure_openai_key, azure_openai_deployment). Configure the corresponding secrets in your repository. Link the relevant issue in the PR description using one of the supported keywords (e.g., Closes #<number>).

Key features of PR Intent Checker GitHub Action (MCP Server Packaged)

  • Packages GitHub MCP server inside Docker.
  • Analyzes PR diffs using Azure OpenAI.
  • Compares code changes against linked issue requirements.
  • Posts AI results as PR comments.
  • Outputs PASS/FAIL with explanation.

Use cases of PR Intent Checker GitHub Action (MCP Server Packaged)

  • Verify PR code matches issue requirements before merge.
  • Catch early intent drift in code changes.
  • Automate code review for requirement alignment.
  • Enforce consistency between PRs and project goals.

常见问题

1

How does the action link a PR to an issue?

It scans the PR description for keywords like `Closes`, `Fixes`, or `Resolves` followed by the issue number (e.g., `Closes #4`). It also checks timeline events for linked issues.

2

What Azure OpenAI credentials are required?

You must provide three secrets: `AZURE_OPENAI_ENDPOINT` (your endpoint URL), `AZURE_OPENAI_KEY` (API key), and `AZURE_OPENAI_DEPLOYMENT` (the model deployment name).

3

What permissions does the workflow need?

The workflow requires `contents: read`, `pull-requests: write`, and `issues: read`.

4

What are the supported issue linking formats?

Formats include `Closes #<number>`, `Closes: #<number>`, `Fixes #<number>`, `Fixes: #<number>`, `Resolves #<number>`, `Resolves: #<number>`, and their past-tense variants (e.g., `Closed`, `Fixed`, `Resolved`). Case is ignored.

5

How does the action communicate with the GitHub API?

The Python script inside the Docker container communicates with the background MCP server via stdin/stdout using JSON-RPC messages. It does not rely on external libraries like PyGithub.

评论

版本控制 分类下的更多 MCP 服务器