mirror of
https://github.com/andwati/dokploy.git
synced 2026-10-18 03:02:56 +00:00
chore: add SKILL.md for issue reproduction and verification process
chore: create .mcp.json for MCP server configuration
This commit is contained in:
@@ -0,0 +1,39 @@
|
|||||||
|
---
|
||||||
|
name: fix-issue
|
||||||
|
description: Implement a GitHub issue with reproduction and verification
|
||||||
|
allowed-tools: Bash, Edit, Write, Read, Glob, Grep, mcp__playwright__*, mcp__dokploy__*
|
||||||
|
---
|
||||||
|
|
||||||
|
The issue number is passed as $1. An isolated instance is running at $DOKPLOY_BASE_URL.
|
||||||
|
|
||||||
|
## Tools
|
||||||
|
|
||||||
|
- `mcp__dokploy__*` — the Dokploy API of the running instance. Use it to set up
|
||||||
|
state (create a project, an app, an env var) and to verify backend behavior.
|
||||||
|
Search for the tool you need; they are not all loaded upfront.
|
||||||
|
- `mcp__playwright__*` — the browser at $DOKPLOY_BASE_URL. Use it for anything
|
||||||
|
a user would see or click.
|
||||||
|
|
||||||
|
Pick by where the bug lives, not by convenience:
|
||||||
|
|
||||||
|
- Bug in the UI (rendering, forms, navigation, state) → reproduce in Playwright.
|
||||||
|
The API returning correct data proves nothing here.
|
||||||
|
- Bug in the API, deploy logic, or data → reproduce with the Dokploy MCP.
|
||||||
|
A green screenshot proves nothing here.
|
||||||
|
- Unclear → do both.
|
||||||
|
|
||||||
|
Use the MCP to reach the state you need quickly, then verify in the UI. Do not
|
||||||
|
click through ten screens to create a project the API can create in one call.
|
||||||
|
|
||||||
|
## Steps
|
||||||
|
|
||||||
|
1. Run `gh issue view $1` and read the full issue, including comments.
|
||||||
|
2. Reproduce the bug with the appropriate tool. If you cannot reproduce it,
|
||||||
|
comment on the issue explaining what you tried and STOP.
|
||||||
|
Do not implement anything.
|
||||||
|
3. Implement the fix. Keep the change minimal and scoped to the issue.
|
||||||
|
4. Run `pnpm test`, then re-run the same reproduction from step 2.
|
||||||
|
5. Only if both pass: commit and run `gh pr create`. The PR description must
|
||||||
|
include the before/after reproduction steps and reference the issue.
|
||||||
|
|
||||||
|
Never skip step 2. A fix you cannot reproduce and then verify is not a fix.
|
||||||
Reference in New Issue
Block a user