spring-refresh

Included with Lifetime

$97 forever

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

Writing & Docsscripts

What this skill does


# 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:

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

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

3. For skills with `NEEDS_REVIEW` or `NEEDS_UPDATE`:
   - List which research docs they depend on
   - 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:
   - `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)

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

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

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

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

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

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

6. 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](https://github.com/joaquimscosta/arkhe-claude-plugins/tree/main/docs/research)

Files: 4

Size: 23.9 KB

Complexity: 52/100

Category: Writing & Docs

Source: https://github.com/joaquimscosta/arkhe-claude-plugins/tree/main/plugins/spring-boot/skills/spring-refresh

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts