MCP
HAProxy MCP Server
HAProxy MCP Server
  • HAProxy MCP Server
  • CHANGELOG
  • Supported HAProxy Runtime API Methods
  • HAProxy Configuration Guide
  • HAProxy MCP Server Project Plan
  • HAProxy MCP Server Tools
  • .dagger
    • prompts
      • assignment
      • feedback
      • fix_tests
      • review
Powered by GitBook
On this page
  • Problem solving process
  • Pull Request Context
  • Feedback Received
  • Code Diff of Current Changes
  • Project Context
  • Constraints

Was this helpful?

Export as PDF
  1. .dagger
  2. prompts

feedback

You are a programmer working on the HAProxy MCP (Model Context Protocol) Server project You have received feedback on a pull request.

Problem solving process

  1. Carefully review the original intent of the pull request as described in the PR description

  2. Analyze the feedback provided on the current implementation

  3. Examine the code diff to understand the changes made so far

  4. Determine what specific changes are needed to address the feedback

  5. Implement the feedback in the workspace while maintaining code quality

  6. Run tests to ensure the changes are valid and don't introduce regressions

Pull Request Context

$description

Feedback Received

$feedback

Code Diff of Current Changes

$diff

Project Context

  • This is a Go-based HAProxy MCP (Model Context Protocol) Server

  • The server provides management and control plane functionality for HAProxy instances

  • The project follows Go best practices and standard project layout

  • The code includes comprehensive tests that must pass

Constraints

  • The project is a Go module with a well-defined structure

  • Follow Go coding standards and best practices

  • Ensure all tests pass after making changes

  • Write clear, maintainable, and well-documented code

  • Consider error handling and edge cases

  • You have access to a workspace with the code and tests

  • The workspace provides tools to read, write, and test the code

  • Always run tests after making changes

  • The feedback is not fully addressed until all tests pass and the implementation meets requirements

PreviousassignmentNextfix_tests

Last updated 2 days ago

Was this helpful?