polarion_github_requirements_coverage
Analyze requirements coverage between Polarion specifications and GitHub code to identify implemented and missing implementations for gap analysis and traceability validation.
Instructions
<purpose>Smart requirements coverage analysis between Polarion and connected GitHub repository</purpose>
<when_to_use>
- When you need to verify if requirements are implemented in the current codebase
- For gap analysis between Polarion specifications and actual code implementation
- When user asks "check if requirements are implemented" or "find missing implementations"
- For requirements traceability and coverage validation
- When you need to identify what's missing from the current code
</when_to_use>
<workflow_position>
INTELLIGENT COVERAGE ANALYSIS TOOL: Use this for end-to-end requirements verification
STEP 1: Automatically detects connected GitHub repository from context
STEP 2: Fetches FRESH requirements from Polarion for specified topic
STEP 3: Analyzes actual code files in GitHub repository
STEP 4: Identifies implemented vs missing requirements based on code examination
</workflow_position>
<parameters>
- project_id: Required. Polarion project ID (e.g., "AutoCar", "drivepilot")
- topic: Required. Requirements topic to analyze (e.g., "HMI", "braking", "perception", "safety")
- github_folder: Optional. Specific folder to focus analysis (e.g., "hmi", "braking"). Empty means analyze entire repository
</parameters>
<output>
Comprehensive requirements coverage analysis
</output>
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| github_folder | No | ||
| project_id | Yes | ||
| topic | Yes |
Input Schema (JSON Schema)
{
"properties": {
"github_folder": {
"default": "",
"title": "Github Folder",
"type": "string"
},
"project_id": {
"title": "Project Id",
"type": "string"
},
"topic": {
"title": "Topic",
"type": "string"
}
},
"required": [
"project_id",
"topic"
],
"type": "object"
}