nabledge-dev

Nablarch knowledge development

Documents

• Development Status - Current progress and roadmap
• Design Document - Architecture and design details
• ToBe Image - Activity mapping and role division with Nabledge
• Mapping File Design - Documentation mapping specification
• Mapping Files v6 - Documentation to knowledge file mapping (Excel)

Prerequisites

• WSL2 / Ubuntu
• CA certificate (if behind corporate proxy)

Setup

1. Install CA Certificate (for proxy environments)

sudo cp /path/to/your/ca.crt /usr/local/share/ca-certificates/ca.crt
sudo update-ca-certificates

2. Environment Setup

./setup.sh
cp .env.example .env
# Edit .env and set your credentials

Getting Started

source .env
claude

Branch Strategy

This repository uses a single-branch development workflow:

Branch	Purpose	Workflow
main	Development branch	All development work is merged here via pull requests. Changes automatically sync to nablarch/nabledge:develop

Development Flow

Feature branch → main (via PR) → nablarch/nabledge:develop (auto-sync)

When changes are pushed to the main branch, GitHub Actions automatically:

1. Transforms the skill content to marketplace plugin structure
2. Syncs to the develop branch in nablarch/nabledge

This allows:

• Continuous integration of development work to nabledge:develop
• Users can test unreleased features from the develop branch
• Clear separation: nabledge-dev for development, nabledge for distribution

Testing Development Version

To test the latest development version from nablarch/nabledge:develop:

1. Download setup script:

   curl -sSL https://raw.githubusercontent.com/nablarch/nabledge/develop/setup-6-cc.sh > /tmp/setup-6-cc.sh

2. Install from develop branch:

   NABLEDGE_BRANCH=develop bash /tmp/setup-6-cc.sh

3. Verify installation:

   claude-code
   # In Claude Code session:
   /nabledge-6

Release Procedure

Releases are managed in the nablarch/nabledge repository, not here.

In nablarch/nabledge repository:

1. Prepare release - Update version files and CHANGELOG in develop branch
2. Create release PR - From develop to main branch
3. Merge and tag - After review, merge PR and create version tag
4. Publish release - Create GitHub release with release notes

See .claude/rules/release.md for detailed release workflow.

Development

Custom Slash Commands

This repository provides custom slash commands to streamline development workflow:

/hi - Full Development Workflow

Execute complete workflow from issue/PR to review request:

/hi 123        # Start work on issue #123
/hi 456        # Resume work on issue/PR #456
/hi            # Interactive selection

Creates branch, implements changes, runs tests, creates PR. Use with issue# to start new work, or PR# to resume existing work.

/fb - Review Feedback Response

Respond to PR review feedback:

/fb 456        # Respond to reviews on PR #456
/fb            # Auto-detect from current branch

Fetches comments, implements fixes, commits, replies to reviewers.

/bb - Merge and Cleanup

Approve and merge PR, cleanup branch:

/bb 456        # Merge PR #456 and delete branch
/bb            # Auto-detect from current branch

Approves PR, merges, detaches HEAD to main, deletes branch.

Testing nabledge Skills

Use the nabledge-test skill to validate nabledge-6 functionality:

# Run a single test scenario
/nabledge-test 6 handlers-001

# Run all test scenarios
/nabledge-test 6 --all

# Run tests for a specific category
/nabledge-test 6 --category handlers

Test scenarios are defined in .claude/skills/nabledge-test/scenarios/nabledge-6/scenarios.json. Results are saved to .pr/xxxxx/test-<id>-<timestamp>.md.

The nabledge-test skill uses skill-creator's evaluation procedures to verify:

• Correct workflow execution (keyword-search, section-judgement)
• Expected keywords present in responses
• Relevant sections identified from knowledge files
• Knowledge file content used (not LLM training data)

Feedback

For published nabledge skills

Report issues or request features in nablarch/nabledge Issues - this helps users search and find solutions.

For unreleased development work

Report issues or discuss changes in nablarch/nabledge-dev Issues.