spring-refresh

Spring Boot Skill Freshness

Check whether Spring Boot skills are current with the latest research docs.

Arguments

Parse $ARGUMENTS for mode:

• check (default, no args) — Scan and report freshness
• refresh — Update research docs via deep-research, then report
• update <skill-name> — Help update a specific skill's content

Mode: check

1. Run the freshness scanner:

python3 ${CLAUDE_SKILL_DIR}/scripts/scan_skill_freshness.py --format json ${CLAUDE_SKILL_DIR}/../..

1. Parse the JSON output and present a formatted report with:
2. Research doc staleness table (file, version, last updated, age, status)
3. Skill drift table (name, target version, last modified, research date, drift, status)
4. Summary counts (up-to-date, needs review, needs update)

1. For skills with NEEDS_REVIEW or NEEDS_UPDATE:
2. List which research docs they depend on
3. Suggest running /spring-refresh update <skill-name> for each

Mode: refresh

1. For each Spring Boot research doc, invoke the Skill tool with core:deep-research to refresh:
2. refresh spring-boot-ecosystem (for ecosystem-research.md)
3. refresh spring-boot-ddd-implementation (for ddd-implementation.md)
4. refresh spring-boot-security-observability-testing (for security-observability-testing.md)

1. After all research docs are refreshed, run the check mode to produce the updated report.

1. 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.

Mode: update \<skill-name\>

1. Run check mode first to identify drift status for the specified skill.

1. Read the research docs that map to this skill:
2. spring-boot-ecosystem-research.md → scanner, verify, web-api, data-ddd, modulith, domain-driven-design
3. spring-boot-ddd-implementation.md → domain-driven-design, data-ddd, web-api, modulith
4. spring-boot-security-observability-testing.md → security, observability, testing

1. Read the skill's current content: SKILL.md, EXAMPLES.md, TROUBLESHOOTING.md, and all files in references/.

1. Compare research content against skill content. Identify:
2. New APIs or patterns in research not covered in the skill
3. Deprecated patterns in the skill that research has replaced
4. Version-specific changes (e.g., new Spring Boot minor version features)

1. Present proposed changes to the user for confirmation before editing.

1. After updates, bump the spring-boot-version field if targeting a new version.

Output Format

## Spring Boot Skill Freshness Report

### Research Documents
| Document | Version | Updated | Age | Status |
|----------|---------|---------|-----|--------|

### Skills
| Skill | Target | Modified | Research | Drift | Status |
|-------|--------|----------|----------|-------|--------|

### Recommendations
- [actionable items]

References

• [EXAMPLES.md](EXAMPLES.md) for usage examples
• [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for common issues
• Research docs (local): docs/research/spring-boot-*.md
• Research docs on GitHub