Getting started

What to prepare

• A small ABAP artifact with a clear purpose, such as a report with selection parameters or one class with a few methods.
• A concrete expectation for the first run: explain, suggest a small improvement, draft a test, or create a simple file.
• A limit for the change scope so the first proposal does not modify several responsibilities at once.

Recommended workflow

1. Provide contextCreate a small file or import one ABAP artifact first. Keep the first run intentionally limited so you can understand the file tree, editor, chat, and review surface separately.
2. Describe the task preciselyAsk the assistant for a clearly scoped change. Good starter tasks are analyzing one method, proposing a small extraction, or creating a test class for one isolated case.
3. Review the changeOpen the proposed files, inspect the diff and reasoning, and only accept changes you can understand technically and functionally. Pay special attention to whether new files are created at expected paths.

Example prompt

A good first prompt is small, concrete, and reviewable.

Analyze the existing report ZREP_ORDER_EXPORT.
Briefly explain the main logic and suggest one small, safe improvement.
Only create changes that I can review clearly in the diff.

Review checklist

• Is the proposal small enough to review completely in the diff?
• Are all newly created files under `src` named in a technically plausible way?
• Did the assistant expose assumptions instead of silently inventing business behavior?