Describe the feature or problem you’d like to solve

Currently, the GitHub MCP Server does not automatically apply the PULL_REQUEST_TEMPLATE.md when contributors open a new pull request. This leads to inconsistencies in PR formatting, missing information, and reduces the overall quality and standardization of pull request submissions.

This problem becomes more critical as the project scales with more contributors or cross-functional teams, where consistent pull request descriptions are essential for effective code reviews, audits, and automation tools.

Proposed solution

Ensure that the MCP Server repository correctly enforces the usage of the PULL_REQUEST_TEMPLATE.md file by:

• Placing the template in the correct path: .github/PULL_REQUEST_TEMPLATE.md
• Ensuring that there is no conflicting .github/pull_request_template/ folder if not required
• Validating that the template is properly recognized by GitHub and is automatically loaded in the PR description field
• Optionally, enhancing the template with pre-filled checklist items for QA, testing, and reviewers

This improvement would:

• Promote consistency and clarity across all pull requests
• Improve onboarding for new contributors by providing structured guidance
• Reduce back-and-forth communication due to missing information in PRs
• Enable better integration with CI workflows or automation that depend on structured PR data

Example prompts or workflows (for tools/toolsets only)

• When a developer opens a new pull request, GitHub automatically pre-fills the PR description with the standardized template content (e.g., description, checklist, testing steps).
• A CI tool (e.g., GitHub Actions or Danger) can parse the PR body to ensure that all checklist items are completed before merging.
• A reviewer can immediately understand the context, test plan, and purpose of the PR without needing to request additional information.
• Contributors from other teams (e.g., QA, Design) can quickly verify PRs because required sections (e.g., screenshots, test cases) are always included.

Additional context

N/A