Cursor rule

1---
2description:
3globs:
4alwaysApply: false
5---
6# Execute Planned Task Commits from GitHub Issue
7 
8 
9**Your Primary Goal: Systematically execute the step-by-step plan defined in a specified GitHub issue (the issue number is provided by the user). Create each commit as planned and verify its success.**
10 
11## File Existence Check
12 
13Verify that the provided issue exists before starting:
14 
15```bash
16ls . docs
17```
18 
19If the issue is missing or inaccessible, stop and notify the user.
20 
21## Workflow for Each Commit in the Issue:
22 
231.  **Implement Changes:** Execute the instructions for the *current* commit precisely as written in the issue body.
242.  **Verify Thoroughly:** BEFORE committing, perform **ALL** specified **Verification** steps for that commit. Confirm successful completion of each verification step.
253.  **Commit Changes:** Stage all implemented changes. Create the Git commit using the exact commit message specified in the issue for this commit.
264.  **Record Progress (Post-Commit):** Immediately after the `git commit` command succeeds:
27    - Run `gh issue comment <issue-number> --body "✅ <commit-sha> <commit-message>"` so the hash and full message are recorded.
28    - **Example Comment:** `✅ a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0 feat: add login (#42)`
295.  **Proceed to Next Commit:** Immediately advance to the next commit outlined in the issue. **Do not ask for feedback or confirmation.** Continue this cycle until all commits in the issue are processed.
30 
31## Definition of "Task Completion"
32 
33A task is considered **"Complete"** if and ONLY if all the following conditions are met:
341.  **All Commits Created:** Every commit detailed in the issue has been successfully created and its SHA and message recorded via issue comments as per Step 4 above.
352.  **Tests Pass:** All automated tests relevant to the changes made pass successfully.
363.  **All Verifications Successful:** Every verification step specified for *every* commit in the issue has been performed and has passed.
37 
38## Actions After Entire Task is Complete:
39 
401.  **Invoke Project Update Rule:** Once the entire task is Complete (as defined above), you MUST then load and meticulously follow all instructions within the `.cursor/rules/project-update-rules.mdc` file.
412.  **Provide Feedback (to `project-update-rules.mdc`):** When prompted by the `project-update-rules.mdc` (or as part of its process), provide the following specific information:
42    - Any failures encountered during the task execution that could have been prevented (and how).
43    - Any significant changes to overall project behavior or developer workflow/expectations resulting from the completed task.
44 
45## Strict Output Constraints:
46 
47- **NO Conversational Output Between Commits:** Absolutely no commentary, summaries, or status updates between individual commits of the task.
48- **Focus on Execution Artifacts:** Your outputs during the commit cycle should ONLY be:
49    - The results of commands executed (if they produce output).
50    - The diffs of file changes applied.
51    - The comment posted to the issue (showing the added SHA and commit message).
52- **After Task Completion:** The only further output is that generated by following `.cursor/rules/project-update-rules.mdc`.
53- **AVOID Unnecessary Chatter:** Do not output messages like the following example:
54```
55    <bad_example>
56    Commit 1 complete and verified. Tests green. Verification successful.
57    Moving to Commit 2 now.
58    </bad_example>
59```
60 
61**REMEMBER: Execute the task plan with precision. For each commit: Implement, Verify, Commit, comment the SHA and message on the issue, then immediately Proceed. No chatter. Once all commits are done and verified, trigger the project update rule.**
62