Check Spring Boot skill content freshness against latest research and flag skills needing updates. Use when running /spring-refresh, or when user mentions "refresh spring skills", "spring boot update check", "skill freshness", "stale spring content", "update spring boot skills".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Check whether Spring Boot skills are current with the latest research docs.
Parse $ARGUMENTS for mode:
check (default, no args) — Scan and report freshnessrefresh — Update research docs via deep-research, then reportupdate <skill-name> — Help update a specific skill's contentpython3 ${CLAUDE_SKILL_DIR}/scripts/scan_skill_freshness.py --format json ${CLAUDE_SKILL_DIR}/../..
Parse the JSON output and present a formatted report with:
For skills with NEEDS_REVIEW or NEEDS_UPDATE:
/spring-refresh update <skill-name> for eachFor each Spring Boot research doc, invoke the Skill tool with core:deep-research to refresh:
refresh spring-boot-ecosystem (for ecosystem-research.md)refresh spring-boot-ddd-implementation (for ddd-implementation.md)refresh spring-boot-security-observability-testing (for security-observability-testing.md)After all research docs are refreshed, run the check mode to produce the updated report.
Show a before/after comparison of research doc dates.
Fallback: If the deep-research skill is not available, skip the research refresh and run check mode only. Inform the user they can manually update research docs.
Run check mode first to identify drift status for the specified skill.
Read the research docs that map to this skill:
spring-boot-ecosystem-research.md → scanner, verify, web-api, data-ddd, modulith, domain-driven-designspring-boot-ddd-implementation.md → domain-driven-design, data-ddd, web-api, modulithspring-boot-security-observability-testing.md → security, observability, testingRead the skill's current content: SKILL.md, EXAMPLES.md, TROUBLESHOOTING.md, and all files in references/.
Compare research content against skill content. Identify:
Present proposed changes to the user for confirmation before editing.
After updates, bump the spring-boot-version field if targeting a new version.
## Spring Boot Skill Freshness Report
### Research Documents
| Document | Version | Updated | Age | Status |
|----------|---------|---------|-----|--------|
### Skills
| Skill | Target | Modified | Research | Drift | Status |
|-------|--------|----------|----------|-------|--------|
### Recommendations
- [actionable items]
docs/research/spring-boot-*.mdNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create, review, and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, quality review, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", "review ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.
The English summary is being prepared. Showing the original description.
Analyze system architecture, module structure, API contracts, data models, and code patterns. Use when designing systems, reviewing module boundaries, evaluating API designs, analyzing data models, checking pattern conformance, tracing decisions, or reviewing frontend architecture. Triggers: "architecture", "module design", "API design", "data model", "boundaries", "patterns", "decisions", "frontend architecture".
The English summary is being prepared. Showing the original description.
Converts natural-language descriptions or UI spec files into optimized Google Stitch prompts. Use when creating, refining, or validating design directives for Google Stitch. Use when user says "create a Stitch prompt", "optimize this for Stitch", "convert this spec to a Stitch prompt", "write a UI prompt", or mentions Google Stitch prompt authoring. Follows Stitch best practices with short, directive prompts focused on screens, structure, and visual hierarchy.
The English summary is being prepared. Showing the original description.
Zero-dependency live-preview server providing an agent↔browser bidirectional companion. Watches a content directory, wraps HTML fragments in a frame template, broadcasts live-reload over WebSocket, and captures browser-side click events to a JSONL file. Use when an agent needs to show HTML to the user in a browser and react to clicks — mockups, design exploration, gallery browsing, multi-select choices, prototype iteration. Triggered by "live preview", "browser companion", "preview server", "browser mockup", "show in browser", "arkhe-preview", or any skill that wants to write HTML fragments and have the user see them reload in real time.
The English summary is being prepared. Showing the original description.
Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.
The English summary is being prepared. Showing the original description.
Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".
The English summary is being prepared. Showing the original description.