Skip to content

Conversation

@ivanduplenskikh
Copy link
Contributor

@ivanduplenskikh ivanduplenskikh commented Nov 26, 2025

Context

This PR introduces a GitHub Copilot Agent prompt file to help maintain the repository by analyzing issues that can be possibly resolved. This prompt will guide Copilot agents to review and analyze long-standing issues to determine if they've been addressed through code changes, documentation updates, or architectural improvements.

📌 Related WI: AB#2337822


Task Name

N/A - This is a repository maintenance tool, not a pipeline task.


Description

Added a new Copilot agent prompt file (issueresolver.prompt.md) that defines an "Issue Resolution Specialist" agent. This agent is designed to:

  • Review opened issues
  • Investigate whether the reported behavior has been resolved in newer versions
  • Analyze code changes, commit history, and documentation updates
  • Provide structured resolution proposals with customer-friendly communication drafts
  • Help maintain repository health by identifying resolved issues

Risk Assessment (Low / Medium / High)

Low - This change only adds a documentation/prompt file and does not modify any production code, task logic, or runtime behavior. It's a tool for repository maintenance and has no impact on end users.


Change Behind Feature Flag (Yes / No)

No - Not applicable. This is a static prompt file for Copilot agent guidance, not a feature that requires runtime control.


Tech Design / Approach

  • Designed as a structured prompt following GitHub Copilot agent conventions
  • Configured to use Claude Sonnet 4.5 with specific GitHub MCP tools
  • Includes comprehensive guidelines for:
    • Issue analysis methodology
    • Resolution verification process
    • Customer communication templates
    • Confidence-based decision making
  • Emphasizes empathetic, customer-focused communication over simple ticket closure

Documentation Changes Required (Yes/No)

No - The prompt file itself is self-documenting. No additional user-facing documentation is needed.


Unit Tests Added or Updated (Yes / No)

No - Not applicable. This is a prompt configuration file, not executable code.


Additional Testing Performed

Manual review of the prompt structure and content to ensure:

  • Proper frontmatter configuration
  • Clear instructions and constraints
  • Appropriate tone and guidelines
  • Alignment with repository maintenance goals

Logging Added/Updated (Yes/No)

No - Not applicable.


Telemetry Added/Updated (Yes/No)

No - Not applicable.


Rollback Scenario and Process (Yes/No)

Yes - Simple rollback: delete the prompt file or revert the commit. No dependencies or side effects.


Dependency Impact Assessed and Regression Tested (Yes/No)

N/A - This change has no dependencies and cannot cause regressions as it only adds a new prompt file.


Checklist

  • Related issue linked (if applicable)
  • Task version was bumped — not a task change
  • Verified the task behaves as expected — not a task change

@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants