Work on Linear Issue

---

name: resolve-linear-issue
description: You will receive a Linear issue ID, typically in the format of LLL-XX, where Ls are letters and Xs are digits. Your primary goal is to resolve this issue on a new branch and open a pull request (PR) to the main branch.

To accomplish this task, follow these detailed steps:

1. Obtain Issue Context (Step 1)

   • Use the Linear MCP (Merge Code Pull Requests) tool to retrieve the details of the issue.
   • The issue ID is provided at the beginning of this prompt: LLL-XX.

2. Initialize Your Development Environment (Step 2)

   • Ensure you are on the latest version of the main branch by performing a git pull if necessary.
   • Create a new branch in the following format: claude/issue-LLL-XX-short-3-4-word-description-of-the-issue.
   • Checkout to this new branch immediately after creation. All subsequent changes and commits should occur on this new branch only.

3. Research and Plan Solution (Step 3)

   • Thoroughly investigate the codebase with respect to the issue details.
   • Develop a clear implementation plan. If any clarifications are needed regarding the issue, please request them before proceeding.
   • Verify your understanding of the problem and the proposed solution at each planning step.

4. Implement and Commit Changes (Step 4)

   • Begin implementing the changes based on your plan.
   • Use git commit best practices for each commit. Ensure the commit messages are descriptive and follow the conventional commit format.
   • Document any significant decisions or assumptions in the commit messages.

5. Review and Debug (Step 5)

   • After completing the implementation, take a fresh look at your changes.
   • Identify and address any potential issues, bugs, or edge cases that might arise.
   • Ensure the code meets the project's quality and style standards.

6. Create Pull Request (Step 6)

   • Once confident that the changes are free of issues, create a pull request (PR) to the main branch.
   • Provide a clear and concise PR title that accurately describes the change.
   • Draft a PR description that summarizes the issue resolution and the fix provided.
   • Include any relevant details, screenshots, or demonstration links in the PR description.

Please ensure all steps are followed meticulously to maintain a clean and organized development process.