코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.8만건)
Bug diagnosis and fixing specialist - analyzes errors, identifies root causes, provides fixes, and writes regression tests. Use for bug, debug, error, crash, traceback, exception, and regression work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Frontend specialist for React, Next.js, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment. Use for UI, component, page, layout, CSS, Tailwind, and shadcn work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automated CLI-based parallel agent execution — spawn subagents via Gemini CLI, coordinate through MCP Memory, monitor progress, and run verification
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Conventional Commits spec git commits (auto-separate by feature)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze conversation histories from multiple AI tools (Grok, Claude, Codex, Qwen, Cursor, Antigravity) and generate themed daily/period work summaries. Filter by date or time window.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage MCP tools with natural language commands — list, enable, disable tools and tool groups
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Mobile specialist for Flutter, React Native, and Swift native iOS development. Use for mobile app, Flutter, Dart, React Native, Swift, SwiftUI, iOS, Android, Riverpod, swift-openapi-generator, and widget work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern). Use for API, endpoint, REST, database, server, migration, and auth work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured bug diagnosis and fixing workflow — reproduce, diagnose root cause, apply minimal fix, write regression test, and scan for similar patterns
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Session-start briefing: where did I leave off, what is in flight, what needs attention. One tested script reads git, the journal (followups, running work, cadences) and tracked projects and prints every fixed-threshold check that fires; JellyRock's own aggregator adds open PRs, high-engagement bugs, recent bug reports, current-branch CI, pending handoffs, open upstream-watch issues (Jellyfin releases and release candidates, Roku OS), recent ADRs, tech debt and architecture-doc staleness. Ends with one Suggested next move that hands off to /log, /done, /issue-triage, /runtime-triage, /ci-triage or /server-upgrade. Mandated by AGENTS.md's catchup-discipline rule: run at the start of any genuine new session, after a multi-day gap, or whenever you ask what the state of the world is.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update a pull request: a typed title (`fix:`, `feat:` … from `scripts/lib/pr-title.js`, which places the change in CHANGELOG.md), category labels chosen by judgment, a concise body from `.github/pull_request_template.md` that reads as the squash commit message, and one skill-owned "review notes" comment for the detail reviewers want but `git log` doesn't. Detects an existing open PR for the current branch and routes to update-mode (diff title/labels/body/comment, ask, then apply) instead of duplicating; aborts cleanly on merged/closed PRs. Scans branch + commits for related issues, falls back to `gh` issue search, surfaces architecture docs whose related-files were touched, and runs the four-pillar judgment passes (tech-debt scan, decision-shape detect, followup capture) so journal hygiene is part of shipping rather than a separate manual step. Required for all PRs in this repo; it supersedes any default PR-creation flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft a GitHub issue body for the JellyRock repo from a Reddit/Discord post or free-form bug report and submit it via forge.sh. Reads the YAML form templates under .github/ISSUE_TEMPLATE/ to know which fields are required, fills them by extracting from the input, asks for any missing required fields, validates the body matches the chosen template's schema, then runs forge.sh issue create with the auto-labels the template defines. Use when you have a user report (paste from anywhere) and want to formalize it into a properly-structured GitHub issue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add a new translation key to JellyRock's custom JSON i18n system. Walks locale/CLAUDE.md (pick the right key prefix, add to locale/custom/en_US.json alphabetically, handle plurals via Zero/One/Many suffixes, handle placeholders via indexed {0} {1}, add ISO-639-2 aliases for track-language keys, run npm run lint:translations + lint:language-coverage). Use when adding a new user-visible string. The BSC plugin watches en_US.json and regenerates the translationKeys constants live, so the BS-side reference becomes available without a manual codegen step.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided workflow for standing up a new Jellyfin apiVersion tier (V3, V4, …) in JellyRock when an upstream release restructures the API enough to need a new `if m.getApiVersion() >= N` dispatch level. Wraps the "Add an API tier" recipe in docs/dev/jellyfin-server-versioning.md and walks every surface that must move together (the boundary map in YAML, its BrightScript twin `resolveApiVersion()`, the `sdkVN.bs` endpoints, the dispatch branches, the device profile, the manifest tier clamp, and the validators), stopping at each step so the tier split cannot land half-built. Use when proactive RC/master triage (via `/server-upgrade <rc-or-unstable>`) shows a breaking API shift that a per-method `>= N` branch must cover. Not for routine endpoint additions inside an existing tier (those use the existing `>= 2` shape directly).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use on any bug, test failure, or unexpected behavior before proposing a fix. Enforces four-phase root-cause investigation — reproduce, pattern-match, hypothesize, fix — with a hard rule against symptom patches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs an isolated checkout. Verify the worktree location, keep mutable environments and build outputs local, and run only authorized setup and checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write git commit messages for this repository following the `[area]` prefix convention. Use when composing or reviewing a commit message in jxck.io.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds currency hedging models with rolling forward programs, option-based strategies, and cross-hedge analysis for international portfolios. Use when designing hedge programs, analyzing hedge ratios, or evaluating FX protection costs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structures co-investment reporting with deal-level performance, fee/carry calculations, and co-invest program aggregate analysis. Use when reporting co-invest performance, tracking deal-level returns, or preparing co-invest summaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structures ATM offering programs with sales agent selection, volume limitations, and disclosure requirements. Use when establishing ATM programs, managing ongoing equity issuance, or optimizing capital raising timing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structures warehouse lending for securitization programs with advance rates, eligibility criteria, and ramp-up analysis. Use when managing warehouse lines, structuring ramp facilities, or analyzing warehouse economics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates competition law exposure with market definition, HHI analysis, and remedy estimation for proposed transactions. Use when assessing merger clearance risk, analyzing market concentration, or preparing HSR filings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authoritative reference for working with the released Wandelbots NOVA API v2 in the wandelbots-nova Python SDK. Use whenever a task touches the NOVA API, the generated `wandelbots_api_client` models (`nova.api.models.*`), motion planning requests (`plan_trajectory`, `MotionGroupSetup`, `LimitSet`, `LimitsOverride`), robot limits, or torque/velocity/acceleration/jerk limits. Reach for this skill before guessing field names or assuming a field exists — the installed client reflects the RELEASED API, while nightly specs may contain unreleased fields. Especially relevant for controller-reported limits (e.g. KUKA torque) and any "does field X exist / how is it forwarded to the planner?" question.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open or update one GitHub pull request for the current work: a conventional-commits title and a description that always includes why and benefits, and never a second PR for the same head. Use when the user asks to open a PR, create a pull request, update or refresh the PR description, ship the branch, or "make a PR". On the default branch, create a new branch first. If this head already has a PR, edit it — do not create another. Do not open a PR unless the user asked.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.