6 changed files with 60 additions and 0 deletions
@ -0,0 +1,9 @@ |
|||||||
|
--- |
||||||
|
name: login-to-core |
||||||
|
description: Log in to CORE local using playwright |
||||||
|
--- |
||||||
|
|
||||||
|
Check playwright-cli --help for available commands. |
||||||
|
Navigate to http://localhost:3000. |
||||||
|
Username is 'support@example.com' |
||||||
|
Password is stored inside .env.template as REVIEW_APP_USER_PASSWORD |
||||||
@ -0,0 +1,11 @@ |
|||||||
|
--- |
||||||
|
auto_execution_mode: 0 |
||||||
|
description: Fix failing tests |
||||||
|
--- |
||||||
|
For doing markups of PRs after they've been reviewed: |
||||||
|
1. Use GitHub MCP to find the PR and the status of the last run |
||||||
|
2. Start by summarising each test fail, grouping them by test fails that seem to be from the same root cause |
||||||
|
3. Wait for me to provide any guidance |
||||||
|
4. Then, go through each test fail group one by one, and suggest a fix for the test passing. Provide some example code if possible. |
||||||
|
5. If I say yes, make the change, if I say no, move on to the next test fail. |
||||||
|
6. Do this until all test fails are resolved |
||||||
@ -0,0 +1,11 @@ |
|||||||
|
--- |
||||||
|
auto_execution_mode: 0 |
||||||
|
description: Respond to PR comments |
||||||
|
--- |
||||||
|
For doing markups of PRs after they've been reviewed: |
||||||
|
1. Use GitHub MCP to find the PR and the PR reviews - this should be ones since the last commit |
||||||
|
2. Start by summarising each comment, categorising them into "Small Nitpick", "Bug catch", "Large Refactor" |
||||||
|
3. Wait for me to provide any guidance |
||||||
|
4. Then, go through each comment one by one, asking me if I want to make this change. |
||||||
|
5. If I say yes, make the change, if I say no, move on to the next comment. |
||||||
|
6. Do this until all comments are done |
||||||
@ -0,0 +1,13 @@ |
|||||||
|
--- |
||||||
|
auto_execution_mode: 0 |
||||||
|
description: Raise a pull request for this branch |
||||||
|
--- |
||||||
|
You are a senior software engineer performing raising a pull request for this branch |
||||||
|
|
||||||
|
You need to: |
||||||
|
1. Figure out the ticket number you're working on, this will be in the branch name |
||||||
|
2. Create a pull request for this branch on Github |
||||||
|
3. The title of the pull request should be based on the ticket number and other pull requests |
||||||
|
4. The description should be a summary of the changes, use git diff on main to get the changes. |
||||||
|
5. Follow the description of other PRs raised by me. Copy my writing style. |
||||||
|
6. Assign the pull request to me. Don't add reviewers. |
||||||
@ -0,0 +1,14 @@ |
|||||||
|
--- |
||||||
|
auto_execution_mode: 0 |
||||||
|
description: Take screenshots of what I changed and save them to review-screenshots |
||||||
|
--- |
||||||
|
|
||||||
|
Check playwright-cli --help for available commands. |
||||||
|
Check the git diff to see what changed. |
||||||
|
Figure out what pages could have changed. |
||||||
|
Take screenshots of those pages. A server will be running at http://localhost:3000/. |
||||||
|
Ensure the question text, any error text and the submit button are all visible. |
||||||
|
Save the screenshots to the review-screenshots folder. |
||||||
|
Present them to me for review. Present all at once with links to the screenshots. |
||||||
|
When presenting use `code` to show me the screenshot. |
||||||
|
After I've confirmed them all, run ./clear-review-screenshots.sh. This is a dangerous command. |
||||||
Loading…
Reference in new issue