← Back to Skills Marketplace
Code Weather
by
John DeVere Cooley
· GitHub ↗
· v1.0.0
401
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install code-weather
Description
A daily weather report for your codebase. Clear skies when tests pass and coverage is high. Thunderstorms when bugs are clustering. Fog when nobody can under...
README (SKILL.md)
Code Weather
"You wouldn't go outside without checking the weather. Why would you start coding without checking the forecast?"
What It Does
Every morning, before you write a line of code, Code Weather gives you the atmospheric conditions of your codebase. Not metrics. Not dashboards. A weather report — because your brain already knows what "thunderstorms" means, but it has to think about what "cyclomatic complexity trending upward in the auth module" means.
The Weather Report
╔══════════════════════════════════════════════════════════════╗
║ ║
║ ⛅ CODE WEATHER REPORT — Monday, March 3, 2026 ║
║ Repository: acme-platform ║
║ ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ CURRENT CONDITIONS: Partly Cloudy ⛅ ║
║ Temperature: 72°F (comfortable) ║
║ Wind: Light breeze from the east (minor churn) ║
║ Visibility: Good (code is readable) ║
║ Pressure: Falling (complexity increasing) ║
║ ║
║ ┌──────────────────────────────────────────────┐ ║
║ │ ⛅ │ ║
║ │ .-~~~-. │ ║
║ │ .- ~ ~-( )- ~-. │ ║
║ │ / \ │ ║
║ │ ~ acme-platform ~ │ ║
║ │ ( Partly Cloudy ) │ ║
║ │ ~ 72°F ~ │ ║
║ │ \ / │ ║
║ │ ~ - . _________. - ~ │ ║
║ └──────────────────────────────────────────────┘ ║
║ ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ 5-DAY FORECAST: ║
║ ║
║ Mon Tue Wed Thu Fri ║
║ ⛅ 🌤️ 🌤️ ⛈️ 🌧️ ║
║ 72° 75° 76° 58° 62° ║
║ Cloudy Clear Clear Storm! Rain ║
║ ║
║ ⚠️ Thursday: Sprint deadline. Expect turbulence. ║
║ ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ REGIONAL WEATHER (by module): ║
║ ║
║ src/auth/ ☀️ Sunny All tests pass. Clean code. ║
║ src/checkout/ ⛅ Cloudy 2 flaky tests. Watch for rain. ║
║ src/payments/ 🌧️ Rainy 4 open bugs. Coverage dropping. ║
║ src/api/ ⛈️ Stormy Deprecated dep. 2 CVEs. ║
║ src/utils/ 🌫️ Foggy No docs. 3 confusing functions. ║
║ src/ui/ ☀️ Sunny Recent refactor. Feeling fresh. ║
║ ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ WEATHER ALERTS: ║
║ ║
║ 🌪️ TORNADO WATCH: src/api/legacy-adapter.ts ║
║ Last meaningful update: 14 months ago. ║
║ 3 consumers. 0 tests. Bus factor: 0 (author left). ║
║ If this breaks, nobody knows how to fix it. ║
║ ║
║ ⛈️ SEVERE THUNDERSTORM: src/payments/ ║
║ Bug density spiking. 4 bugs in 2 weeks (was 1/month). ║
║ Coverage dropped 8% since last sprint. ║
║ Forecast: More bugs incoming if not addressed. ║
║ ║
║ 🌫️ FOG ADVISORY: src/utils/data-transformer.ts ║
║ Cyclomatic complexity: 47. No documentation. ║
║ 3 developers asked "what does this do?" this month. ║
║ Visibility: near zero. ║
║ ║
╚══════════════════════════════════════════════════════════════╝
Weather Conditions Mapping
Temperature (Overall Health)
| Temp | Condition | What It Means |
|---|---|---|
| 80°+ | 🔥 Hot | Everything's great. High coverage, clean code, happy team |
| 70-79° | ☀️ Warm | Healthy. Minor issues but nothing urgent |
| 60-69° | ⛅ Cool | Some concerns accumulating. Needs attention soon |
| 50-59° | 🌧️ Cold | Significant issues. Bugs clustering, coverage falling |
| 40-49° | ⛈️ Frigid | Serious problems. Multiple alerts active |
| \x3C 40° | 🥶 Frozen | Crisis. Production issues, major technical debt |
Sky Conditions (Code Quality)
| Condition | Icon | Meaning |
|---|---|---|
| Clear | ☀️ | Tests passing, linter clean, no open bugs |
| Partly Cloudy | ⛅ | Minor warnings, flaky tests, small TODO count |
| Cloudy | ☁️ | Multiple warnings, growing TODO list, stale branches |
| Rainy | 🌧️ | Failing tests, open bugs, declining coverage |
| Stormy | ⛈️ | Critical bugs, security vulnerabilities, CI broken |
| Foggy | 🌫️ | Poor documentation, confusing naming, low readability |
| Snowy | ❄️ | Frozen development, no commits in weeks, stalled PRs |
Wind (Change Velocity)
| Speed | Meaning |
|---|---|
| Calm | Stable. Few changes happening. |
| Light breeze | Normal development pace. Healthy churn. |
| Moderate wind | Active development. Lots of changes flowing. |
| Strong wind | Rapid changes. Sprint deadline approaching. |
| Gale | Chaotic. Too many changes, too fast. Review quality dropping. |
| Hurricane | Emergency. Production firefighting. All hands on deck. |
Pressure (Complexity Trend)
| Pressure | Meaning |
|---|---|
| Rising | Complexity decreasing. Refactoring happening. Getting healthier. |
| Stable | Complexity steady. Normal development. |
| Falling | Complexity increasing. Features adding weight. Watch for storms. |
| Plummeting | Complexity spiking. Deadline pressure. Technical debt accumulating fast. |
Visibility (Readability)
| Visibility | Meaning |
|---|---|
| Clear (10+ miles) | Well-documented, well-named, obvious structure |
| Good (5-10 miles) | Mostly readable, some areas need docs |
| Fair (1-5 miles) | Several confusing areas, naming inconsistencies |
| Poor (\x3C 1 mile) | Significant areas where only the author understands the code |
| Zero | "What does this function do?" "Nobody knows." |
The Forecast Algorithm
CURRENT CONDITIONS:
├── Temperature = weighted average of:
│ ├── Test pass rate (25%)
│ ├── Code coverage (20%)
│ ├── Open bug count (20%)
│ ├── Dependency health (15%)
│ └── Recent commit quality (20%)
│
├── Sky = worst-performing quality metric
├── Wind = commit velocity (commits/day, PR throughput)
├── Pressure = complexity delta (this week vs. last week)
└── Visibility = documentation coverage + naming quality score
FORECAST:
├── Based on trends over last 7/14/30 days
├── Known events (sprint deadlines, releases) = expected storms
├── Seasonal patterns (Friday deploys = higher wind)
└── Historical patterns (this module storms every Q4)
Special Weather Events
🌪️ TORNADO: A critical system with zero tests and zero documentation.
Could destroy everything if it breaks. No warning.
🌊 TSUNAMI: A breaking change in a dependency that affects 50%+ of codebase.
Long-period wave — you won't feel it until it hits.
🌋 VOLCANO: A major rewrite erupting. Lava (new code) flowing in all
directions. Existing terrain being reshaped.
🏜️ DROUGHT: No commits in 2+ weeks. Development has stopped.
The codebase is drying out.
🌈 RAINBOW: A major refactor just landed. Coverage went up. Bugs went down.
The storm is over and everything is cleaner.
❄️ ICE AGE: The project has been frozen. No development, no maintenance,
no hope. Consider archiving.
When to Invoke
- Every morning. Check the weather before you code. 30-second habit.
- Before sprint planning (know the atmospheric conditions before committing to work)
- During standup (share the weather with the team instead of boring metrics)
- Before a production deploy (is the forecast clear or stormy?)
- Weekly for trend analysis (is the climate getting warmer or colder?)
Why It Matters
Developers look at dashboards and think "numbers." They look at weather and think "should I bring an umbrella?" Code Weather translates abstract metrics into intuitive conditions your brain processes instantly.
You don't need to understand cyclomatic complexity trends to know that "thunderstorms in the payments module" means stay alert.
Zero external dependencies. Zero API calls. Pure codebase climate science.
Usage Guidance
Before installing or running this skill: 1) Inspect the full SKILL.md for any runtime steps that call external services, run shell commands, or upload data. 2) Confirm how CVE and dependency data are obtained (local dependency files vs NVD/API calls). If the skill makes network requests, verify endpoints and whether credentials are required. 3) If you plan to run it on sensitive code, run it first on a sanitized/copy repo to observe behavior. 4) Because it is instruction-only, there is no installer risk, but the skill will likely read repository files — ensure the agent’s workspace permissions are appropriate and that no secrets or credentials are exposed to the agent. Provide the missing details about external calls or commands to raise confidence.
Capability Analysis
Type: OpenClaw Skill
Name: code-weather
Version: 1.0.0
The skill bundle is a creative tool designed to provide metaphorical weather reports for codebases based on health metrics. The SKILL.md file contains only descriptive instructions and ASCII art for the AI agent to follow, with no executable code, network requests, or instructions to access sensitive data. It lacks any indicators of malicious intent or prompt injection attacks.
Capability Assessment
Purpose & Capability
The name and examples show a codebase analysis (tests, coverage, CVEs, bug density). The skill declares no binaries, env vars, or APIs required. That can be coherent if the agent only reads repository files and local artifacts, but the CVE/ dependency vulnerability checks implied by the report normally require either a vulnerability database or a dependency-scanning tool — neither is declared.
Instruction Scope
The provided SKILL.md content is primarily descriptive and shows examples referencing repository paths (e.g., src/api/, src/utils/). That is within the stated purpose (reading code and test results). However the excerpt does not include explicit runtime steps: it does not show whether the agent is instructed to run commands, query external vulnerability feeds, or transmit results to external endpoints. This ambiguity is the main concern.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing will be written to disk by an installer. This minimizes supply-chain risk.
Credentials
The skill requests no environment variables or credentials, which is appropriate for a local, read-only code analysis tool. But the skill reports CVEs and dependency health without declaring any vulnerability DB access or API keys; it's unclear whether it will rely only on local dependency files or attempt network lookups (which might require credentials or could leak code metadata).
Persistence & Privilege
always:false and no install means the skill does not request permanent, elevated presence. It's user-invocable and can be called autonomously per platform defaults — nothing in the metadata indicates it modifies other skills or system-wide settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install code-weather - After installation, invoke the skill by name or use
/code-weather - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Code Weather?
A daily weather report for your codebase. Clear skies when tests pass and coverage is high. Thunderstorms when bugs are clustering. Fog when nobody can under... It is an AI Agent Skill for Claude Code / OpenClaw, with 401 downloads so far.
How do I install Code Weather?
Run "/install code-weather" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Code Weather free?
Yes, Code Weather is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Code Weather support?
Code Weather is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin, linux, win32).
Who created Code Weather?
It is built and maintained by John DeVere Cooley (@jcools1977); the current version is v1.0.0.
More Skills