load-context

Extract domain context from Kotlin Spring codebases into structured summaries.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill load-context
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: load-context
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/eng/spring/skills/load-context
Command: npx skills add https://github.com/semicolon-devteam/semo --skill load-context

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

๋„๋ฉ”์ธ/๊ธฐ๋Šฅ์˜ ์ปจํ…์ŠคํŠธ๋ฅผ ๋น ๋ฅด๊ฒŒ ํŒŒ์•…ํ•˜๊ณ , ๋ช…ํ™•ํ•œ ๋ฌธ์„œ๋กœ ๊ณต์œ ํ•ฉ๋‹ˆ๋‹ค.

Core Features & Use Cases

  • ์ปจํ…์ŠคํŠธ ์š”์•ฝ: Spec ๋ฌธ์„œ, ์ฝ”๋“œ ๊ตฌ์กฐ, ์ด๋ ฅ, ์ด์Šˆ ์š”์•ฝ ์ œ๊ณต
  • ์—ฐ๊ณ„ ์ œ์•ˆ: ๋‹ค์Œ ์ž‘์—…์œผ๋กœ์˜ ์ž๋™ ์ œ์•ˆ ์ œ๊ณต

Quick Start

๋„๋ฉ”์ธ ์ปจํ…์ŠคํŠธ๋ฅผ ๋น ๋ฅด๊ฒŒ ํŒŒ์•…ํ•˜๊ณ  ๊ณต์œ ํ•ฉ๋‹ˆ๋‹ค.

Frequently Asked Questions about load-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I quickly understand domain context from source code and documentation?โ–ผ

Domain context analysis aggregates spec documents, source code structure, git history, related issues, and test status into a standardized summary. This Skill extracts and structures that information for Kotlin Spring codebases, enabling rapid onboarding, debugging, and change-impact assessment across domain modules.

Can I analyze domain context without modifying code?โ–ผ

Yes. This Skill performs read-only analysis, extracting context by examining existing specs, code structure, git history, and test results without making changes. It produces structured summaries suitable for code review, onboarding, and architectural understanding.

How do I get a domain summary that includes recent changes and test coverage?โ–ผ

The Skill aggregates spec summaries, code structure, recent git changes, open issues, and test results into one context document. Optional modes (--deep, --spec-only, --code-only, --history) let you focus on specific aspects of the domain.

What's the best way to share domain knowledge across a team working on a Kotlin Spring codebase?โ–ผ

Generate a standardized context summary that captures specs, code organization, recent changes, and test status. This produces a unified reference that onboarding developers, reviewers, and maintainers can use to understand feature scope and dependencies quickly.

Does this work for analyzing change impact across multiple domain modules?โ–ผ

Yes. The Skill analyzes domain/{domain} structures, integrating code changes, git history, related issues, and test results to assess impact across modules. This supports change-impact analysis and debugging workflows.

What if I need only specifications or code structure without historical data?โ–ผ

Use optional modes to customize output: --spec-only extracts documentation, --code-only focuses on structure, --history surfaces git changes. This lets you tailor context extraction to your immediate need.