Files

fujie 6b39531fbc feat(skills): add 6 generalized AI-driven development skills

- version-bumper: automated multi-file version synchronization
- plugin-scaffolder: standardized 12-language i18n template generation
- doc-mirror-sync: automated README to docs mirroring
- i18n-validator: dictionary key alignment analysis via AST
- gh-issue-replier: professional English reply with star-check logic
- gh-issue-scheduler: unanswered issue audit and action planning

2026-02-24 16:02:01 +08:00

2.4 KiB

Raw Blame History

Issue Reply Templates

Use these templates to craft professional English replies. Adjust placeholders like @username, v1.2.x, and [commit hash] as needed.

1. Acknowledging a New Issue

Use when you first see an issue and want to let the user know you are working on it.

"Thank you for reporting this! I'm looking into it right now."
"Thanks for bringing this to my attention. I'll try to reproduce this behavior and get back to you shortly."

2. Requesting More Information

Use when you need logs or specific details to fix the bug.

"Could you please provide the 'Original' vs 'Normalized' content from your browser console logs (F12)? It would help a lot in debugging."
"It would be very helpful if you could share the specific Markdown text that triggered this issue."

3. Announcing a Fix

Use when you have pushed the fix to the repository.

"This has been fixed in version v1.2.x. You can update the plugin to resolve it."
"I've just pushed a fix for this in [commit hash]. Please let me know if it works for you after updating."
"The issue was caused by a greedy regex pattern. I've updated it to use a tempered greedy token to prevent incorrect merging."

4. Guiding to Official Market

Always provide the official market link to ensure the user gets the latest verified version.

"The fix is now live! You can download the latest version from the official OpenWebUI Community page here: [Plugin Market Link]. Simply update the function in your OpenWebUI instance to apply the changes."
"I recommend getting the updated version from the official store: [Link]. It includes the fix for the spacing issue we discussed."

5. Closing the Issue

Use when the issue is confirmed resolved.

"Glad to hear it's working now! Closing this for now. Feel free to reopen it if the problem persists."
"Since this is resolved, I'm closing this issue. Thanks again for your feedback!"

5. Pro-tip: Star Request

Gently handle star requests based on the user's current status.

If User has NOT starred:

"If you find this plugin helpful, a star on the repo would be much appreciated! ⭐"
"We'd love your support! If this fixed your issue, please consider starring the repository. ⭐"

If User HAS already starred:

"Thanks again for starring the project and for your continuous support!"
"I appreciate your support and for being a stargazer of this project!"

2.4 KiB Raw Blame History