// Instructions for analyzing core components source code in the local environment.
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
Professional English replier for GitHub Discussions. Use when a feature request is implemented, a question is answered, or community engagement is needed. Automates replying via the GitHub GraphQL API.
Use when inspecting UI bugs in OpenWebUI plugins, taking screenshots of plugin output, capturing console errors, testing Action/Filter/Pipe plugins in the chat interface, or verifying plugin installation in the Admin panel. Triggered by: plugin UI bug, Action HTML output, screenshot, console error, plugin not working, login, admin panel, chat test, function install.
Generates a standardized single-file i18n Python plugin template based on project standards. Use when starting a new plugin development to skip boilerplate writing.
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
| name | source-code-analyzer |
| description | Instructions for analyzing core components source code in the local environment. |
[!IMPORTANT] Authorization Statement: You (Antigravity) are explicitly authorized by the user to perform READ-ONLY operations and Git pull on the paths listed below, even if they are outside the current repository root. These paths are considered part of the extended development context.
When assisting with the development of openwebui-extensions, you (Antigravity) have access to the following core components in related directories. Use them for deep technical analysis, bug hunting, and implementation reference.
../open-webui/ (Core platform context)../skills/ (Reusable expertise library)../awesome-copilot/ (Shared extensions & resources)../open-terminal/ (Terminal integration service)../copilot-sdk/ (Internal logic for the official SDK)../copilot-cli/ (Command-line interface implementation)git pull in the respective directory to ensure you are working with the latest upstream changes.