Loading...
Loading...
Found 9,271 Skills
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A questions answered with their defaults. Pass --doc-scan-only to scan README.md and env.dist for outdated content without modifying any files. Use when the user wants to migrate an App Builder project from the Integration Starter Kit or Checkout Starter Kit to the App Management approach, or mentions upgrading their Adobe Commerce extension architecture.
Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.
Diagnose what state one open PR is actually in — unfinished plan steps, missing review, unresolved conversations, red CI, base conflicts, missing QA evidence, merge-ready — then run the matching chain of om-* skills in order and publish a status report. Use for "finish PR 123", "what is left on PR 123", "drive PR 123 to the end".
Used to discover the minimal change that a target truly accomplishes: put identity, boundaries, quality, optimization metrics, and implementations in parentheses, keep only the concise core of 'who or what goes from A to B', compress it into the minimal structural formula of interpretable variables, verify whether it is truly decontextualized through cross-domain migration, and save it as a validated Org note. USE WHEN the user says '/ljg-is', 'What is the essence of X', 'The One', 'Find the essence of the target', 'Essence definition', 'Minimum function', 'What exactly is transformed into what', or asks to distinguish qualifiers from the core. NOT FOR asking about reasons (use ljg-think), seeking motifs or causal structures (use ljg-structure), or casually saying 'essentially' in a sentence.
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
Turn the current conversation into a spec (Problem, Solution, User Stories, Decisions) and publish it as a GitHub issue. Validates a feature before any code is written.
Load context for a task: read the spec/ticket, explore the codebase surface, and present the task context to the user. The user controls implementation.