source-code-analyzer
Skill326 starsChanged 8 months agoMITView on GitHub
Instructions for analyzing core components source code in the local environment.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Fu-Jie/awesome-openwebuiword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Fu-Jie/awesome-openwebui★ 326100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- community-announcerSkill
- doc-mirror-syncSkill
- gh-discussion-replierSkill
- gh-issue-replierSkill
- gh-issue-schedulerSkill
- i18n-validatorSkill
- playwright-openwebuiSkill
- plugin-scaffolderSkill
- pr-reviewerSkill
- pr-submitterSkill
- publish-no-version-bumpSkill
- release-finalizerSkill
- release-prepSkill
- version-bumperSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
When assisting with the development of openwebui-extensions, you (Antigravity) have access to the following core components in related …
- Distinctive: line 29
Pull Before Analysis: BEFORE reading files or analyzing logic in these directories, you MUST proactively execute or recommend a git pull in …
- Distinctive: line 30
Path Verification: Always verify the exists of the path before attempting to read it.
- Distinctive: line 31
Reference Logic: When a user's request involves core platform behavior (OpenWebUI API, SDK internals), prioritize searching these …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Source Code Analyzer Skill
[!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.
Core Component Paths
Global / General (Relevant to all projects)
- Open WebUI:
../open-webui/(Core platform context) - Skills:
../skills/(Reusable expertise library) - Awesome Copilot:
../awesome-copilot/(Shared extensions & resources) - Open Terminal:
../open-terminal/(Terminal integration service)
Plugin-Specific (Relevant to GitHub Copilot SDK)
- Copilot SDK:
../copilot-sdk/(Internal logic for the official SDK) - Copilot CLI:
../copilot-cli/(Command-line interface implementation)
Mandatory Workflow
- Pull Before Analysis: BEFORE reading files or analyzing logic in these directories, you MUST proactively execute or recommend a
git pullin the respective directory to ensure you are working with the latest upstream changes. - Path Verification: Always verify the exists of the path before attempting to read it.
- Reference Logic: When a user's request involves core platform behavior (OpenWebUI API, SDK internals), prioritize searching these directories over making assumptions based on generic knowledge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.