Commit PR
samuelclay/NewsBlur
A skill your agent uses when the user runs /commit-pr, says "commit and push", "open a PR", "ship this", asks to update an existing PR with new changes, or asks to resolve PR review comments in the…
Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface.
Install Understand Project
$ npx skills add ossappscollective/oss-weather --skill understand-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ossappscollective/oss-weather understand-project --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/understand-project .claude/skills/understand-project && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "understand-project" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-project into .claude/skills/understand-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understand-project", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-projectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ossappscollective/oss-weather --skill understand-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ossappscollective/oss-weather understand-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/understand-project .agents/skills/understand-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "understand-project" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-project into .agents/skills/understand-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understand-project", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ossappscollective/oss-weather --skill understand-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ossappscollective/oss-weather understand-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/understand-project .cursor/skills/understand-project && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "understand-project" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-project into .cursor/skills/understand-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understand-project", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ossappscollective/oss-weather.git --path .claude/skills/understand-project--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ossappscollective/oss-weather --skill understand-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ossappscollective/oss-weather understand-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/understand-project .gemini/skills/understand-project && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "understand-project" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-project into .gemini/skills/understand-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understand-project", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ossappscollective/oss-weather understand-projectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ossappscollective/oss-weather --skill understand-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/understand-project .github/skills/understand-project && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "understand-project" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-project into .github/skills/understand-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understand-project", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ossappscollective/oss-weather --skill understand-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ossappscollective/oss-weather understand-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ossappscollective/oss-weather.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/understand-project .opencode/skills/understand-project && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "understand-project" agent skill from https://github.com/ossappscollective/oss-weather/tree/main/.claude/skills/understand-project into .opencode/skills/understand-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understand-project", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
understand-project- GitHub stars
- 456
- Token cost
- ~576 tokens
- SKILL.md length
- 256 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface.
- Works in 5 steps: Learn the layout that applies. App code… → Find a similar existing implementation.… → Identify reusable assets — existing… → …
- Development work in your project
- SKILL.md covers Steps and Bias
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Understand Project is an agent skill from ossappscollective/oss-weather. Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface. Internal helper invoked by feat / fix (both modes) — not meant to be run on its own.
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Svelte, Android and iOS. The repository describes itself as: An OSS weather app for iOS/Android. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/understand-project”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Learn the layout that applies. App code is under app/: .svelte screens/components/modals live in app/components// (feature dirs: camera…
- Find a similar existing implementation. Glob/Grep for a .svelte component or a service that solves a comparable problem. Read 1-2…
- Identify reusable assets — existing components in app/components/common/ and app/components/widgets/, svelte stores…
- Map the touch surface — every file, component, service, model, i18n key that needs to change. Trace data flow and callers (service…
- Check third-party libraries — when a library is involved (@nativescript-community/*, @akylas/*, svelte-native, sqlite/kiss-orm, …), use…
What it can do on your machine
Read from SKILL.md and the folder at commit 42715ad. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Understand Project loads about 576 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 256 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ossappscollective/oss-weather at commit 42715ad, republished under its MIT licence (© ossappscollective). 256 words, ~576 tokens.
Download SKILL.mdSave it as
.claude/skills/understand-project/SKILL.md (or your agent's skills folder).- name
- understand-project
- description
- Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface. Internal helper invoked by feat / fix (both modes) — not meant to be run on its own.
- disable-model-invocation
- true
Ground every plan and implementation in code that already exists. A plan that says "follows the same pattern as app/components/edit/DocumentEdit.svelte" beats one describing an abstraction in the abstract — the executor gets low cognitive load and a working reference. This is the method; the calling skill says what to build.
Steps
- Learn the layout that applies. App code is under
app/:.sveltescreens/components/modals live inapp/components/<feature>/(feature dirs:camera,edit,list,ocr,pdf,pkpass,qrcode,security,settings,view,common,widgets); domain logic lives in service singletons underapp/services/(documents.ts,sync.ts,ocr.ts,security.ts, …); data models inapp/models/; helpers inapp/utils/,app/helpers/,app/transformers/; strings inapp/i18n/; SCSS themes inapp/themes/. Platform splits use.android.ts/.ios.ts. - Find a similar existing implementation. Glob/Grep for a
.sveltecomponent or a service that solves a comparable problem. Read 1-2 end-to-end so you can point at them by path. - Identify reusable assets — existing components in
app/components/common/andapp/components/widgets/, svelte stores (app/utils/svelte/store.ts), service singletons, models, and utils/helpers. Reuse these by name rather than inventing new ones. - Map the touch surface — every file, component, service, model, i18n key that needs to change. Trace data flow and callers (service singletons are shared, so a change ripples) so nothing is missed.
- Check third-party libraries — when a library is involved (
@nativescript-community/*,@akylas/*, svelte-native, sqlite/kiss-orm, …), use Context7 for version-matched docs before assuming an API.
Bias
Pick the simplest, cleanest solution: reuse existing patterns/components/hooks, fewest files touched, smallest new surface. If a clever approach and a boring approach reach the same outcome, choose the boring one.
© ossappscollective, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/understand-project of ossappscollective/oss-weather.
Open the folder on GitHubat commit 42715ad
Compare with similar skills
Understand Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Understand Project this skillossappscollective/oss-weather | 456 | — | ~576 | Automated safety check: Pass | MIT | |
| Commit PRsamuelclay/NewsBlur | 7.6k | — | ~4.1k | Automated safety check: Pass | MIT | |
| jscpd Code Migration Trackerkucherenko/jscpd | 6.4k | — | ~5k | Automated safety check: Pass | MIT | |
| Codebase Comparison with jscpdkucherenko/jscpd | 6.4k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Code Guidelinesgetsentry/sentry-react-native | 1.8k | — | ~3.2k | Automated safety check: Pass | MIT | |
| ExecuTorch Build Guidepytorch/executorch | 5.1k | — | ~2.3k | Automated safety check: Notes | Custom licence |
Similar skills
jscpd Code Migration Tracker
kucherenko/jscpd
Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.
Codebase Comparison with jscpd
kucherenko/jscpd
Compares two folders function by function with jscpd --compare, across languages if needed, and explains which functions match and which have no counterpart.
- Official
Code Guidelines
getsentry/sentry-react-native
Enforce Sentry React Native SDK code guidelines for implementation, refactoring, and review.
ExecuTorch Build Guide
pytorch/executorch
Builds ExecuTorch from source: the Python package, C++ runtime, model runners, Android and iOS cross-compilation and backend-specific builds, with environment checks.
Canvas
Bitterbot-AI/bitterbot-desktop
Display and control HTML content on connected Bitterbot nodes (Mac, iOS, Android) via the canvas host server.
More from ossappscollective/oss-weather
All 8 skills in this repoCommit
ossappscollective/oss-weather
MANDATORY skill for ALL commits. An agent skill from ossappscollective/oss-weather.
Open PR
ossappscollective/oss-weather
MANDATORY skill for ALL pull requests. An agent skill from ossappscollective/oss-weather.
Feat
ossappscollective/oss-weather
Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with --investigate.
Fix
ossappscollective/oss-weather
Debug and fix any non-trivial issue end-to-end, OR triage a GitHub bug issue read-only.
Investigate Contract
ossappscollective/oss-weather
Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes.
Branch Check
ossappscollective/oss-weather
Ensure you're on a correct working branch off up-to-date main before planning or editing — starting from a GitHub issue when one is in play.
Related
Categories
Questions about Understand Project
What does Understand Project do?
Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface. Understand Project is an agent skill from ossappscollective/oss-weather. Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface.
When should I use Understand Project?
Understand Project fits situations like: development work in your project.
How do I install Understand Project in Claude Code?
Run `npx skills add ossappscollective/oss-weather --skill understand-project -a claude-code`. Or copy the skill folder (.claude/skills/understand-project in ossappscollective/oss-weather) into .claude/skills/understand-project in your project. Claude Code loads it when a task matches its description.
How do I install Understand Project in Codex?
Run `npx skills add ossappscollective/oss-weather --skill understand-project -a codex`. Or copy the skill folder (.claude/skills/understand-project in ossappscollective/oss-weather) into .agents/skills/understand-project in your project. Codex loads it when a task matches its description.
Can I use Understand Project in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ossappscollective/oss-weather --skill understand-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/understand-project, .gemini/skills/understand-project, .github/skills/understand-project and .opencode/skills/understand-project in your project.
What does Understand Project need to run?
SKILL.md names no scripts, command-line tools or credentials: Understand Project is instructions for the agent only.
Does Understand Project access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Understand Project safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Understand Project use?
Understand Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Understand Project use?
About 576 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Understand Project?
Skills that share tags, products or a category with Understand Project: Commit PR (samuelclay/NewsBlur, 7.6k stars), jscpd Code Migration Tracker (kucherenko/jscpd, 6.4k stars), Codebase Comparison with jscpd (kucherenko/jscpd, 6.4k stars) and Code Guidelines (getsentry/sentry-react-native, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Understand Project?
ossappscollective (a GitHub organization) maintains it in ossappscollective/oss-weather, which has 456 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: ossappscollective/oss-weather on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.