{\n "label": "Examples",\n "position": 3,\n "link": {\n "type": "generated-index"\n }\n}

---\ntitle: Code Development Examples\ndescription: Examples of implementing features, fixing bugs, and writing tests\n---\n\n# Code Development Examples\n\nMyCoder can assist with a wide range of code development tasks, from implementing new features to fixing bugs and improving existing code. This page showcases real-world examples of effective prompts for these scenarios.\n\n## Implementing Feature Requests\n\n### Example: Implementing Recommendations from an Issue\n\n```\nCan you implement the recommendations 2 and 3 from issue #44? You can look at the CI Github Actions workflow in ../mycoder-websites/.github as guide to setting up a similar CI action that validates the build and runs lint, etc for this repo.\n```\n\n**Why this works well:**\n- References specific recommendations from an existing issue\n- Points to an example implementation in another repository as a reference\n- Clearly defines the scope (recommendations 2 and 3)\n- Provides context about the expected outcome (CI action for build validation and linting)\n\n**Technique:** Referencing existing issues and providing examples from other parts of the codebase helps MyCoder understand both the requirements and the implementation style.\n\n## Architectural Changes and Refactoring\n\n### Example: Refactoring an SDK Implementation\n\n```\nRecently this project was converted from using the Anthropic SDK directly to using the Vercel AI SDK. Since then it has created reliability problems. That change was made 4 days ago in this PR: https://github.com/drivecore/mycoder/pull/55/files\n\nAnd it was built upon by adding support for ollama, grok/xai and openai in subsequent PRs. I would like to back out the adoption of the Vercel AI SDK, both the 'ai' npm library as well as the '@ai-sdk' npm libraries and thus also back out support for Ollama, OpenAI and Grok.\n\nIn the future I will add back these but the Vercel AI SDK is not working well. While we back this out I would like to, as we re-implement using the Anthropic SDK, I would like to keep some level of abstraction around the specific LLM.\n\nThus I would like to have our own Message type and it should have system, user, assistant, tool_use, tool_result sub-types with their respective fields. We can base it on the Vercel AI SDK. And then we should implement a generic generateText() type that takes messages and the tools and other standard LLM settings and returns a new set of messages - just as anthropic's SDK does.\n\nWe can have an Anthropic-specific function that takes the API key + the model and returns a generateText() function that meets the generic type. Thus we can isolate the Anthropic specific code from the rest of the application making it easier to support other models in the future.\n\nThe anthropic specific implementation of generateText will have to convert from the generic messages to anthropics specific type of messages and after text completion, it will need to convert back. This shouldn't be too involved.\n\nWe can skip token caching on the first go around, but lets create both an issue for this main conversion I've described as well as follow on issues to add token caching as well as OpenAI and Ollama support. You can check out old branches of the code here if that helps you analyze the code to understand.\n\nI would like a plan of implementation as a comment on the first issue - the main conversion away from Vercel AI SDK.\n```\n\n**Why this works well:**\n- Provides detailed background on the current implementation\n- References specific PRs for context\n- Clearly outlines the desired architecture with specific components\n- Explains the rationale behind the changes\n- Specifies what to include now vs. future additions\n- Requests both implementation issues and a plan\n\n**Technique:** For complex architectural changes, providing detailed context and a clear vision of the desired outcome helps MyCoder understand both the technical requirements and the reasoning behind them.\n\n## Debugging and Troubleshooting\n\n### Example: Investigating Build Configuration Issues\n\n```\nWhen I run this command \"pnpm --filter @web3dsurvey/api-server build\" in the current directory, it runs into an error because one of the packages in this mono-repo upon which @web3dsurvey/api-server is dependent is not built, but I am confused because I thought that pnpm would automatically build packages that are depended upon.\n\nI must have some part of the configuration of the current project incorrect right? Can you create an issue for this and then investigate. You can use the command \"pnpm clean:dist\" to reset the package to its non-built state.\n```\n\n**Why this works well:**\n- Describes the specific command that's failing\n- Explains the expected behavior and the actual outcome\n- Shares the developer's hypothesis about the cause\n- Provides a command for reproducing the issue\n- Asks for both an issue creation and an investigation\n\n**Technique:** When troubleshooting, providing MyCoder with the exact commands, expected behavior, and reproduction steps helps it diagnose and fix the issue more effectively.\n\n### Example: Investigating CI Failures\n\n```\nIt seems that the latest GitHub action failed, can you investigate it and make a GitHub issue with the problem and then push a PR that fixes the issue? Please wait for the new GitHub action to complete before declaring success.\n```\n\n**Why this works well:**\n- Identifies a specific problem (GitHub action failure)\n- Requests a complete workflow: investigation, issue creation, and fix implementation\n- Sets clear expectations for verification (waiting for the GitHub action to complete)\n\n**Technique:** Asking MyCoder to handle the full cycle from investigation to fix helps ensure that the problem is properly understood and addressed.\n

---\ntitle: Code Review and Analysis Examples\ndescription: Using MyCoder to review PRs, analyze code quality, and suggest improvements\n---\n\n# Code Review and Analysis Examples\n\nMyCoder is excellent at reviewing code, analyzing PRs, and providing feedback on potential improvements. This page showcases real-world examples of effective prompts for these scenarios.\n\n## PR Review and Analysis\n\n### Example: Reviewing a PR for Potential Duplication\n\n```\nIn the current PR #45, which fixes issue #44 and it is also currently checked out as the current branch, there isn't duplication of the checks are there? In your writeup you say that \"added pre-push hook with the same validation\". It seems that we have both a pre-commit hook and a pre-push hook that do the same thing? Won't that slow things down?\n```\n\n**Why this works well:**\n- References a specific PR and issue\n- Quotes specific text from the PR description\n- Asks a focused question about a potential issue (duplication)\n- Expresses concern about a specific impact (performance slowdown)\n\n**Technique:** When reviewing PRs, asking MyCoder targeted questions about specific aspects helps surface potential issues that might not be immediately obvious.\n\n## Identifying Configuration Issues\n\n### Example: Reviewing Package Manager Configuration\n\n```\nI think that the github action workflows and maybe the docker build are still making assumptions about using npm rather than pnpm. Can you look at ../Business/drivecore/mycoder-websites as an example of docker files that use pnpm and also github action workflows that use pnpm and adapt the current project to use that style. Please create a github issue and then once the task is complete please submit a PR.\n```\n\n**Why this works well:**\n- Identifies a specific concern (npm vs. pnpm assumptions)\n- Points to a reference implementation with the desired approach\n- Clearly defines the expected deliverables (GitHub issue and PR)\n- Provides context about the current state and desired outcome\n\n**Technique:** Asking MyCoder to compare configurations across projects helps identify inconsistencies and standardize approaches.\n\n## UI and Design Review\n\n### Example: Requesting UI Improvements\n\n```\nCan you make the blue that is used for the links to be a little more dark-grey blue? And can you remove the underline from links by default? Please create a Github issue for this and a PR.\n```\n\n**Why this works well:**\n- Makes specific, focused requests for UI changes\n- Clearly describes the desired outcome\n- Specifies the process (create an issue and PR)\n\n**Technique:** For UI changes, being specific about the desired visual outcome helps MyCoder implement changes that match your expectations.\n