abapify

Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.

Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Use when the user invokes /act on a PR/MR or /act <context> with context ∈ {pr, plan, backlog, harvest}. Resolves threads in product code (or posts a substantive in-thread reply), commits, then closes threads. Never resolve-only. Harvest (collecting threads) lives in /harvest; triage (priority / grouping / wontfix) lives in /backlog. /act is the fix loop, not the collect or triage.

Domain-agnostic AI-native scenario runner (e2e-agent CLI). Scenarios are markdown prompts; evidence is written by the CLI. Use when the user invokes /e2e or asks to run a live scenario test and collect evidence under .e2e/results/. Agents use only e2e-agent commands — never import internal framework modules.

Use when the user invokes /harvest on a PR or runs `harvest:pr` / `harvest:batch`. Collects unresolved PR review threads into .agents/review-debt/harvests/*.jsonl on PR merge (or via workflow_dispatch). Does not run during /act and does not open a harvest bot PR — new files are append-only paths pushed straight to main. Downstream consumers: /backlog (triage), /act (batch fix). Harvest is a one-way collect, not a fix loop.

Actionable improvement items derived from experience and retrospectives. Items live in .agents/backlog/.

Unified agent memory. Use /remember to store facts, experience, observations, and mental-models in .agents/memory/.

Reflect on current session and record experience. /retrospect = remember. --plan = + backlog item. --fix = + implement now.

OpenADT product layer — fetch, proxy, transport choice (SDK default), MCP stub. Use when implementing or debugging ADT requests.

CodeScene setup and usage — CI delta analysis, local CLI, CS_ACCESS_TOKEN, Docker image, troubleshooting 403s and secret visibility.

How to consume a GitHub issue body as an agent task prompt. The 9-section template, the lifecycle, the failure modes.

The 12 design principles this codebase is built on. Read first, before any task.

Spec-driven development — the practice of writing the spec before the code. With the 9-section template and the three pnpm spec-check gates.

Differences and deterministic behavior of the mock ADT server used by adt-bench smoke runs.

How to return a strict scenario result JSON with evidence and no extra prose.

Test-driven loop for ABAP — inspect, change, check syntax, run unit tests, diagnose, fix.

Standard ABAP object workflow (discover, create or edit, check, activate, validate).