From sustainable-code-skill-setup
Sustainability-aware development companion. Use during daily coding to check that new features, changes, and commits follow green coding practices. Activates when the user mentions green review, sustainability check before commit, eco-friendly code review, or green coding during development.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sustainable-code-skill-setup:gc-devThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Sustainability checklist for your daily development workflow. Use this during feature development, before commits, and during code reviews.
Sustainability checklist for your daily development workflow. Use this during feature development, before commits, and during code reviews.
When invoked without arguments, run the quick check on recently changed files.
git diff --name-only HEAD~1 # or git diff --staged --name-only
For each changed source file (JS, TS, PHP, Python, Java):
creedengo_check MCP tool to scan for energy-wasteful patternsIf package.json, composer.json, requirements.txt, or similar changed:
If images, fonts, or media files changed:
## Green Check: [branch/commit]
### Code patterns
| File | Issues | Severity |
|------|--------|----------|
| ... | ... | ... |
### Dependencies
- New deps: [list or "none"]
- Bundle impact: [estimated]
### Assets
- New/changed assets: [list or "none"]
- Optimization: [status]
### Verdict
[PASS] Ready to commit — no sustainability concerns
[WARN] Minor issues found — consider fixing before commit
[FAIL] Significant issues — fix before committing
### Actions needed
1. ...
### Methodology
- Code patterns: Creedengo green code rules (green-code-initiative/creedengo-rules-specifications)
- Dependency check: bundle size analysis via [tool]
- Asset check: format and compression best practices per WSG 3.x guidelines
When invoked with /gc-dev feature [description], provide a sustainability-aware development plan:
Based on the feature description, recommend specific patterns from the Green Software Foundation catalog:
## Sustainability Plan: [feature]
### Before coding
- [ ] Evaluate if the feature is necessary (less code = less carbon)
- [ ] Choose the lightest dependencies possible
- [ ] Plan caching strategy for data fetches
### During coding
- [ ] Use lazy loading for non-critical resources
- [ ] Minimize network requests (batch, cache, deduplicate)
- [ ] Avoid blocking the main thread
- [ ] Use efficient data structures and algorithms
- [ ] Add appropriate cache headers
### Before committing
- [ ] Run /gc-dev to check changed files
- [ ] No unused imports or dead code
- [ ] Images optimized (WebP/AVIF, correct dimensions)
- [ ] No console.log in production code
### Before PR
- [ ] Bundle size within budget
- [ ] Run /gc-check-sustainability on affected pages
- [ ] Update wsg-compliance.json if architecture changed
When invoked with /gc-dev review, analyze the current PR diff for sustainability:
git diff main...HEAD
## Green PR Review
### Summary
[1-2 sentence sustainability assessment]
### Findings
| Category | Status | Details |
|----------|--------|---------|
| Dependencies | ok/warn/fail | ... |
| Bundle size | ok/warn/fail | ... |
| Network efficiency | ok/warn/fail | ... |
| Asset optimization | ok/warn/fail | ... |
| Code patterns | ok/warn/fail | ... |
| Accessibility | ok/warn/fail | ... |
### Recommendations
1. ...
### Methodology and sources
- Code patterns: Creedengo green code rules
- Green patterns: Green Software Foundation Patterns Catalog (patterns.greensoftware.foundation)
- WSG reference: W3C Web Sustainability Guidelines 1.0
After presenting the report (quick check, feature plan, or PR review), automatically run /gc-verify in quick mode. This triggers a Chain-of-Verification (CoVe) process: extract claims from the report, generate adversarial questions, answer each independently, and present findings under a ## Verification (CoVe) heading.
/gc-setup — full 9-phase sustainability audit (run once at project start)/gc-measure-sci — measure carbon intensity for a specific operation/gc-check-sustainability — quick WSG + hosting + code patterns check/gc-estimate-emissions — estimate page or sitemap CO2 emissionsProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub fullo/claude-plugins-marketplace --plugin sustainable-code-skill-setup