ch4570
UserSpecialists in sync. Portable skills, task-aware model routing, and independent sessions for Codex and Claude Code.
Categories
Indexed Skills (49)
agent-eval
Evaluate a new or changed agent or skill before merge with NVIDIA SkillEvaluator evidence and adversarial review.
architecture-review-workflow
Review MSA, modular-monolith, and multi-module boundaries by combining system architecture, application architecture, DDD, and code-topology evidence. Use for service decomposition, module extraction, dependency-direction, data ownership, integration contracts, or architecture changes that need boundary-by-boundary findings.
backend-code-review-workflow
Orchestrate a consolidated backend review across Kotlin/Spring correctness, refactoring, design patterns, object-oriented design, and security. Use for pull requests, diffs, or backend modules that need one severity-gated report without losing specialist dissent.
code-authoring-router
Route generic feature, bug-fix, refactor, and implementation requests to installed code-authoring skills after detecting repository stack evidence. Use even when the user only names the desired behavior and does not mention Kotlin, Spring, PostgreSQL, Microsoft SQL Server, or OpenSearch; do not use for review-only requests.
code-diagram-extract
Trace a function or feature into a Mermaid flow, sequence, or state diagram with real source-file and line anchors. Use to explain code behavior.
design-pattern-apply
Assess whether a design pattern fits a real axis of change and prescribe its application. Use for pattern selection or composition/inheritance decisions; reject over-design.
diagram-styler
Render an existing Mermaid `.mmd` semantic source into a themed, responsive, accessible SVG while preserving the source and recording renderer provenance in a manifest. Use for light or dark Mermaid styling, document-width SVG output, presentation output, and pre-rendering diagrams for HTML or PDF documents. Do not use to change diagram meaning or to download renderers at runtime.
document-designer
Turn supplied content into a polished, accessible, editable Markdown document with clear structure, typography roles, information hierarchy, tables, callouts, captions, and page-aware layout intent. Use for reports, PRDs, technical documents, memos, and other Markdown-first publications before HTML or PDF rendering. Do not use to render HTML/PDF or to invent missing content.
e2e-report-renderer
Render settled e2e-runner JSON as offline HTML in single-run, trend, or comparison mode when asked to visualize or share E2E results. Preserve input data.
e2e-runner
Run repository E2E or integration tests in an isolated Testcontainers environment; use for E2E, integration, QA, or full test requests.
e2e-scenario-author
Generate or refresh a source-validated E2E scenario catalog for Spring JVM or NestJS after endpoints/listeners change. Authoring only; does not execute tests.
e2e-test-workflow
Orchestrate E2E catalog authoring, API or integration execution, Playwright browser execution, and optional HTML reporting under one run-owned Testcontainers lifecycle. Use when the agent must run a complete or multi-lane E2E verification, refresh and execute the scenario catalog, combine backend and browser evidence, or produce one false-green-safe E2E handoff. Do not use for authoring-only, runner-only, browser-only, or render-only requests that one component skill can satisfy directly.
entity
Scaffold a new JPA entity following project conventions (schema-qualified @Table, composite @EmbeddedId keys, Persistable for JDBC upsert, read-only mirror entities). Use when adding a persisted entity.
explore-dead-code
Quickly find unreferenced dead-code candidates with file/line evidence and confidence. Use for unused functions, classes, exports, files, or 참조 없는 죽은 코드 탐색. Read-only discovery; excludes code deletion and general refactoring.
flyway
Scaffold a Flyway migration SQL file with a build-enforced filename and PostgreSQL conventions. Use when a persistence change (entity/column/index) needs a migration — authored in the SAME change as the entity.
git-flow
Prepare a safe work branch or commit, push, and open a GitLab merge request when the user asks to start, land, or publish implementation work.
harness-propose
Research recent harness-engineering trends, judge them against this repository's current harness, and produce a self-contained HTML improvement proposal under harness/proposals/{date}/. After user approval, reflect accepted items into the living harness/index.html "다음 단계" section (the dated proposal dir is the record; no separate backlog file). Never modifies the harness before approval. Use to level up the harness or run a periodic harness review.
java-spring-review-workflow
Review Java and Spring changes by running the exact Java/Spring correctness reviewer, object-oriented design review, and design-pattern fit review concurrently against one frozen scope, then reconcile them into one evidence-based verdict. Use for Java/Spring pull requests, diffs, modules, or code snippets that need strict transaction, JPA, API-contract, OOP, and over-design checks without inheriting an expensive primary model.
knowledge-audit
Audit the autonomous knowledge lane (.claude/knowledge/auto/) — verify each machine-written candidate against current code, then promote true/reusable ones to the curated knowledge base or discard stale/duplicate/wrong ones. This is the curation half of the autonomous learning loop — it replaces the human approval gate that the Stop auto-learn hook bypasses. Use periodically (or when the auto lane has accumulated candidates) to keep the KB from rotting.
kotlin-code-authoring
Write or modify Kotlin application code while preserving project conventions and readable Kotlin idioms. Use when implementing a feature, bug fix, or refactor in actual Kotlin application source, including Kotlin/Spring modules, even when the user does not name the stack; do not use for Java changes, Gradle build logic, or review-only requests.
kotlin-spring-review-workflow
Run Kotlin/Spring, object-oriented design, design-pattern, and behavior-preserving refactoring reviews against one frozen code scope, then reconcile them into one evidence-based verdict. Use for Kotlin changes, including Kotlin/Spring pull requests, diffs, modules, or code snippets that need a multi-angle design and maintainability review without the broader security scope of a full backend audit.
kotlin-spring-review
Reference knowledge base for reviewing Kotlin + Spring MSA backend code. Provides DDD three-layered and hexagonal architecture rules, Clean Code principles, Kotlin idioms, functional JVM style, Spring best practices, a severity rubric, and an integrated checklist. Use when reviewing Kotlin/Spring code, checking code quality or architecture rules, or when you need Kotlin-Spring review criteria.
learn
Extract reusable, non-obvious insights from the current conversation/work and persist them as team-shared knowledge under .claude/knowledge/ (rule changes are proposed against AGENTS.md or the relevant skill instead). Applies changes only after user approval. Use when a durable lesson, gotcha, domain flow, or decision rationale emerged that future sessions should not have to rediscover.
mapper
Scaffold a manual `object` mapper between a domain model and JPA entity. This project maps by hand, not MapStruct, because entities are immutable. Use when adding model-to-entity or entity-to-model conversion.
mermaid-diagrams
Create or revise editable Mermaid source for version-controlled flowcharts, sequence diagrams, state diagrams, ER diagrams, class diagrams, and simple architecture diagrams. Use when a structural relationship, process, interaction, lifecycle, data model, or small component topology is clearer as a diagram than prose or a table. Do not use for whiteboard aesthetics, pixel-precise branded layouts, charts, or cases where text is clearer.
mssql-code-authoring
Write or modify Microsoft SQL Server and legacy MS-SQL queries, stored procedures, schemas, indexes, and migrations with version and compatibility-level gating, parameter safety, transaction correctness, and operational verification. Use when repository evidence shows SQL Server, T-SQL, Microsoft.Data.SqlClient, System.Data.SqlClient, mssql-jdbc, mssql, or tedious and the task changes a query, persistence path, database object, or migration. Do not use for review-only work or for PostgreSQL, MySQL, or generic ANSI SQL without SQL Server evidence.
nl-sql-query
Use when a user asks a data question in natural language and wants the SQL built, executed (read-only), and results shown — for PostgreSQL/MySQL/MS-SQL via the nl-sql MCP. Explore the schema with tools, then author and run a dialect-appropriate SELECT and present the results.
notion-domain-context
Retrieve cited, read-only evidence from an explicitly connected private Notion workspace for internal domain or policy questions. Exclude sensitive HR/medical/payroll data, writes, repository-local questions, and MCP setup.
oop-design-review
Review object responsibilities, cohesion, encapsulation, and collaboration using SOLID and GRASP. Use for object-oriented design review, not implementation scaffolding.
opensearch-query-review
Review OpenSearch 3.5 search queries. Inspect dynamic bool queries (filter vs query context, builder safety, paging), vector k-NN queries (k/ef_search, efficient filtering, under-fetch, radial, nested), hybrid (normalization/RRF)·neural/sparse/semantic, and search pipelines. Use when authoring/modifying queries or diagnosing search-result/latency problems. Ground claims in the OpenSearch official-docs KB.
opensearch-review-workflow
Run the complete OpenSearch review suite for queries, mappings, vector/search tuning, and operational safety, then synthesize one evidence-based verdict. Use for OpenSearch or Elasticsearch-compatible index, query, migration, relevance, capacity, or performance changes.
opensearch-schema-review
Review OpenSearch 3.5 index mappings/schemas. Check the dynamic policy, text/keyword, multi-field, index/doc_values, _source/derived source, nested cost, knn_vector fields (dimension/ space_type/engine/method/mode), and the Korean nori analyzer. Use when designing/modifying a mapping or reviewing an index schema. Grounds findings in a KB based on the official OpenSearch docs.
pdf-qa
Render every page of an existing PDF to PNG and gate delivery on recorded visual inspection. Use after generating or changing a PDF, before claiming a PDF report, document, diagram, or slide deck is complete, or when diagnosing clipping, overlap, broken glyphs, pagination, page-balance, or table-spacing defects. This skill validates PDFs; it does not author or repair their source.
playwright-e2e
Execute QA-approved browser E2E in a run-owned Node Testcontainers environment. Prove the app/baseURL and stateful endpoints are ephemeral, seed synthetic case data, execute once, verify cleanup, teardown with zero orphans, and report evidence. Use after QA hands off UI scenarios or when asked to run Playwright E2E.
postgres-query-review
Review PostgreSQL queries (SQL) from performance and correctness angles. Inspect execution-plan interpretation, index usability, join method/order, sort/aggregate cost, pagination, parameter binding, and anti-patterns. Use when writing/modifying SQL or diagnosing slow queries. Applies the principles of "Friendly SQL Tuning", verified against the official PostgreSQL documentation.
postgres-review-workflow
Run all PostgreSQL query, migration-risk, and schema-design skills plus operational DBA and data modeling reviewers, then reconcile their advice. Use for SQL, DDL, migrations, data models, performance incidents, or database changes that need one deployability-aware verdict.
postgres-risk-check
Check the risk of a PostgreSQL change (migration/DDL/bulk DML). Inspect DDL lock levels, zero-downtime change patterns (CONCURRENTLY, NOT VALID→VALIDATE), chunking of large backfills, transactions/concurrency/deadlocks, lock/statement timeout, bloat/VACUUM, and rollback/downtime. Use PROACTIVELY when authoring/reviewing a migration, before a production deploy, or for destructive changes such as DROP/type change.
postgres-schema-design
Design and review PostgreSQL tables/schemas. Covers data modeling (entities·relationships·normalization), identifier strategy (natural/surrogate keys), constraints·integrity (PK/FK/UNIQUE/CHECK), type selection, history modeling, and naming conventions. Use when writing new table/migration DDL or reviewing an existing schema. Applies the principles of "Core Data Modeling," validated against the official PostgreSQL documentation.
product-requirements
제품 아이디어, 기능 제안, 사용자 문제를 구현 가능한 제품 요구사항 문서(PRD)로 구체화한다. 제품 범위와 사용자 흐름을 정리하고, 관찰 가능한 기능 요구사항과 Given/When/Then 인수 기준을 연결하거나, 개발 handoff를 준비해야 할 때 사용한다. 아이디어 자체를 구현·배포하거나 외부 시스템을 변경하는 작업에는 사용하지 않는다.
product-ui-design
Design, implement, or review web, mobile, and desktop product interfaces from real product context and the repository's existing design language. Use for pages, flows, components, responsive behavior, interaction states, accessibility, and visual refinement. Reject generic template aesthetics and unverified visual-completion claims. Do not use for document, slide, or technical-diagram styling.
refactoring-catalog
Select behavior-preserving refactorings for demonstrated code smells and give an ordered verification plan. Use when deciding how to improve existing code safely.
repository
Scaffold data access for a domain entity — a JpaRepository interface named *EntityRepository, plus optional *JdbcRepository (bulk ON CONFLICT upsert) and *AggregateRepository (QueryDSL). Use when adding persistence access.
codex-agent-runtime
Record the fail-closed compatibility status of legacy Vulpora catalog-agent execution. This installable negative-contract skill must not run agents, discovery probes, or delegated tasks.
enum
Scaffold a protocol enum in the shared SSOT module with the unknown-value fallback convention. Use when adding a domain/protocol enum shared across modules.
korean-dev-writer
한국어 기술 문서, PR, 리뷰, 코드 주석을 사실과 요구사항을 보존하며 자연스럽고 간결하게 작성·교정한다. 일반 문예 글쓰기나 새 사실 작성에는 사용하지 않는다.
markdown-publisher
Markdown 문서를 편집 가능한 원본과 함께 오프라인 단일 HTML로 발행하고, 요청 시 로컬 Chromium 계열 브라우저로 PDF를 생성한다. 기술 문서, PRD, 메모, 보고서에 executive/technical/minimal 테마를 적용하거나 Markdown을 인쇄 가능한 HTML/PDF로 변환할 때 사용한다. PDF 완료 판정과 페이지별 시각 검수는 pdf-qa로 라우팅한다.
opensearch-code-authoring
Write or modify OpenSearch mappings, Query DSL, vector or hybrid search settings, and reindex plans with relevance, latency, and operational safety. Use when a feature, bug fix, or refactor in a repository detected as OpenSearch touches search behavior, mapping, configuration, or queries, even when the user does not name OpenSearch; do not use for review-only requests.
postgres-code-authoring
Write or modify PostgreSQL queries, schemas, and migrations with parameter safety, data integrity, and operational verification. Use when a feature, bug fix, or refactor in a repository detected as PostgreSQL requires SQL, DDL, indexes, or migrations, even when the user does not name the database; do not use for review-only requests.
request
Scaffold a REST request DTO co-located with its controller, as a validated Kotlin data class. Use when adding a request body for an API endpoint.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.