zhongwei/gh-daveharmswebdev-upkeep-io-upkeep-io-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:18:11 +08:00
commit 7c433e0dfd
14 changed files with 3103 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
commands/refine-issue.md Normal file
View File

@@ -0,0 +1,15 @@
Please refine the following issue: $ARGUMENTS.
Follow these steps:
1. Use `gh issue view` to get the details; pay careful attention to the comments.
2. Look at the codebase and pay attention to pertinent documentation.
3. Look at commit history if needed.
4. **REQUIRED RESEARCH (blocking):**
- Use `mcp__Ref__ref_search_documentation` for technical aspects
- Use `mcp__firecrawl__firecrawl_search` for domain/compliance aspects
- Follow `@shared/research-protocol.md`
- Cite sources in refined issue
5. Ask clarifying questions.
6. Refine and rewrite the issue and save changes.
7. Inform me when that the refinement is completed.

24
commands/work-issue.md Normal file
View File

@@ -0,0 +1,24 @@
Please analyze and fix the GitHub issue(s): $ARGUMENTS.
If multiple issue numbers are provided (space-separated), treat them as related issues to be worked together in a single branch.
Follow these steps:
1. Parse the issue number(s) from the arguments
2. Use `gh issue view <number>` for EACH issue to get details; pay careful attention to comments
3. Create a single git branch for the related issues (e.g., `feature/issues-42-43`)
4. **Before lead-dev begins work:**
- Lead-dev MUST use ref MCP to research any unfamiliar patterns or APIs
- Lead-dev MUST follow `@shared/research-protocol.md`
- Lead-dev MUST document sources consulted in PR description
5. Have the lead dev work the issue(s) following TDD methodology when applicable
6. **Before qa-tester reviews:**
- QA-tester MUST use ref MCP to verify current testing patterns
- QA-tester MUST use playwright MCP for E2E testing
- QA-tester MUST follow `@shared/research-protocol.md`
7. Have the qa-tester check the work, running all unit tests and e2e tests
8. Also validate project build and running the project (front end and back) in dev mode. Errors during build and dev mode is intolerable.
9. If the qa-tester is satisfied, create a PR for me to check (reference ALL issues in PR description)
10. If the qa-tester is not satisfied then pass the work back to lead-dev and keep iterating until the qa-tester is satisfied
Remember to use the GitHub CLI (`gh`) for all GitHub-related tasks.