Skip to content

feat(nabledge-5/6): Add upgrade-check workflow for Nablarch version upgrade impact analysis#251

Draft
kumagoro1202 wants to merge 2 commits intonablarch:mainfrom
kumagoro1202:feat/upgrade-check-workflow
Draft

feat(nabledge-5/6): Add upgrade-check workflow for Nablarch version upgrade impact analysis#251
kumagoro1202 wants to merge 2 commits intonablarch:mainfrom
kumagoro1202:feat/upgrade-check-workflow

Conversation

@kumagoro1202
Copy link
Copy Markdown

@kumagoro1202 kumagoro1202 commented Mar 26, 2026

Summary

This PR adds an upgrade-check workflow to the nabledge-5 and nabledge-6 skills, enabling automated impact analysis when upgrading Nablarch versions.

Added files

nabledge-5:

  • .claude/skills/nabledge-5/workflows/upgrade-check.md
    • 4-step workflow: pom.xml detection → rule-based filter → LLM-assisted evaluation → report generation
  • .claude/skills/nabledge-5/scripts/upgrade-checker.sh
    • Rule-based detection script implementing R1–R8 rules

nabledge-6:

  • .claude/skills/nabledge-6/workflows/upgrade-check.md
    • Same workflow adapted for Nablarch v6 release notes
  • .claude/skills/nabledge-6/scripts/upgrade-checker.sh
    • Rule-based detection script for v6 release notes

Background

Nablarch users often face challenges when assessing upgrade impacts between versions, as they must manually review release notes. This workflow automates the detection process by:

  1. Detecting the current Nablarch version from pom.xml (BOM dependency)
  2. Applying 8 rule-based detection patterns (R1–R8) against release note JSON files
  3. Providing optional LLM-assisted evaluation for the remaining ~12% of items
  4. Generating a structured Markdown impact assessment report

Detection Rules

Rule Detection Target Method
R1 Sections with hints[] containing "システムへの影響あり" Array value match
R2 Sections with title containing "影響がある変更" Partial string match
R3 Warning/Important blocks in section text Regex on Markdown
R4 Table rows with "あり" in the impact column Table parsing
R5 FQCN extraction from backtick notation Regex extraction
R6 Configuration key extraction from backtick notation Regex extraction
R7 Artifact ID extraction from fix-version columns Table parsing
R8 Project source code matching via grep File system search

Analysis Basis

Analysis of all 83 affected items across 25 release note files (v5: 21 files, 75 items; v6: 4 files, 8 items):

  • Rule-based coverage: ~88% (73/83 items)
  • Requires LLM assistance: ~12% (10 items)

Usage

# For Nablarch v5 projects
nabledge-5 upgrade-check --from 5u13 --to 5u18 --project-dir /path/to/project

# For Nablarch v6 projects
nabledge-6 upgrade-check --from 6u1 --to 6u3 --project-dir /path/to/project

…pgrade impact analysis

- Add workflows/upgrade-check.md: 4-step workflow for detecting upgrade impacts
  using rule-based analysis (R1-R8) and optional LLM-assisted evaluation
- Add scripts/upgrade-checker.sh: bash script implementing R1-R8 detection rules
  covering 88% of affected items across v5/v6 release notes
- Update SKILL.md: add upgrade-check workflow entry in Step 0 routing

Based on analysis of 83 affected items (v5: 75, v6: 8) from release notes JSON.
- Move upgrade-check.md and upgrade-checker.sh from nabledge-1.4 to nabledge-5/6
- Release notes JSON is located in knowledge/releases/releases/ within each skill
- Revert nabledge-1.4/SKILL.md to original state (no upgrade-check entry)
- Update nabledge-5/SKILL.md and nabledge-6/SKILL.md with upgrade-check workflow entry
@kumagoro1202 kumagoro1202 changed the title feat(nabledge-1.4): Add upgrade-check workflow for Nablarch version upgrade impact analysis feat(nabledge-5/6): Add upgrade-check workflow for Nablarch version upgrade impact analysis Mar 27, 2026
@kiyotis kiyotis added the enhancement New feature or request label Mar 27, 2026
@kiyotis kiyotis marked this pull request as draft March 30, 2026 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants