Tool to search for issues

[ShreyPaharia]

Implements https://github.com/idosal/git-mcp/issues/112

[idosal]

Thanks for the contribution @ShreyPaharia!

Did you have a chance to test it out? Did the LLMs use it correctly? Did it help them reach a better answer?

[ShreyPaharia]

Thanks for the contribution @ShreyPaharia!

Did you have a chance to test it out? Did the LLMs use it correctly? Did it help them reach a better answer?

Welcome @idosal ! This is definitely helpful! Sharing below an example conversation.

---

User

How to solve the failure in parsing prd for this repo github.com/eyaltoledano/claude-task-master

---

Cursor

Let me help you investigate this issue. First, I'll try to match the library name to get the correct owner and repo information.

Now that I have confirmed the repository information, let me fetch its documentation to understand what might be causing the parsing failure.

I notice that there's no standard documentation available. Let me search through the repository's code to understand its structure and potential PRD-related files.

I notice that there are some issues accessing the repository. Let me check if there are any open issues that might provide more context about this problem.

Let me check the specific issue about PRD parsing failure to understand the problem better.

Based on the issue and comments, I can help explain the PRD parsing failure and provide a solution. Here are the key points:

1. Location Requirements:

• The PRD file must be in one of two locations:
  • Root directory as prd.txt
  • scripts/prd.txt directory
• The file must be named prd.txt (lowercase) not PRD.txt or prd.md

2. Known Issues:

• There are timing out issues with different tools (Roo and others) that don't have the same rules as Cursor
• The issue occurs with both Anthropic and Perplexity APIs
• The error manifests as either:
  • MCP error -32001: Request timed out
  • Schema validation errors
  • Client failure code: 499

To solve this issue:

1. First, ensure your PRD is in the correct location and format:

   • Move your PRD from /specs/design/prd.md to either:
     • /prd.txt (root directory) or
     • /scripts/prd.txt
   • Rename the file to lowercase prd.txt

2. If you're still experiencing timeouts:

   • Try breaking down your PRD into smaller sections if it's large
   • The example in the issue showed a PRD with 87 lines and 1250 tokens, which should be within limits
   • Consider adding more structure to your PRD to make it easier to parse

3. If using the CLI:

   • Make sure you're using the latest version (0.13.2 or newer)
   • Try running the command multiple times as there might be intermittent timeout issues
   • Consider using Cursor instead of other tools as it has better timeout handling

4. If the issue persists:

   • Check that your PRD follows the expected format and structure
   • Try reducing the complexity of your PRD if possible
   • Consider breaking down the PRD parsing into smaller chunks

Would you like me to help you with any specific part of implementing these solutions?