ProfessorGPTProfessorGPT

Security-flagged skill

This skill may contain destructive commands. Do not install, copy, download, or run it before reviewing the skill details and source. Use it deliberately and only in contexts you understand.

Scanner findings

highscript_injectionhighcredential_theft
View source repo ↗
Azure

Code Review

Azure/sap-automation/.github/skills/code-review
Multi-file
AzureAzure· v1.0.0
codingOfficial
Official Provider SkillView repo

Review pull requests in the SAP Deployment Automation Framework. Use when reviewing a diff, a pull request, or staged changes touching Terraform modules, Ansible roles and playbooks, the deployer shell scripts, the Python helpers, or the GitHub Actions workflows. Reviews for correctness, reliability, security, Azure/SAP domain rules, performance, test coverage, and maintainability — in that priority order. Finds defects that change one sibling module and not the other four, widen a network or an

Files5 files
SKILL.md504 lines
Loading editor…

Install

Recommended

One command — your agent picks it up automatically.

Select an AI agent above to see the install command.

or

Manual Install

More steps

Download the archive and add the files to your project manually.

Skill details

Versionv1.0.0
AuthorAzure
Categorycoding
Skill IDAzure/sap-automation/.github/skills/code-review
Files5 files

Related skills

Sdaf Bom SelectionPick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology. Explains where BOMs live in the samples repo (`SAP/` for whole products, `BOM/` for components), decodes the `ms`, `v####`, and `latest` suffix conventions, points at the compatibility guardrails (`supportedPlatforms`, `supportedDBVersions`, `supportedKernels`), and reminds the operator that the download flow needs four explicit BOM keys in `sap-parameters.yaml`. Use when a user says "which BOSdaf Control Plane BootstrapDeploy the SDAF control plane locally: prepare DEPLOYER and LIBRARY tfvars, review the plan, run `deploy_controlplane.sh` per `docs/local/03-00-control-plane.md § Run`, and validate the deployer + library + state hand-off. Grounded in `docs/local/03-00-control-plane.md`. Use when a user says "deploy the SDAF control plane", "run deploy_controlplane.sh", "bootstrap SDAF from an empty subscription", "install the deployer" or "create the SAP library". Do NOT use for workload zone (see sdaf-workloadSdaf Failure TriageTriage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in `docs/local/troubleshooting.md`, and hand off to the stage-owning skill for retry. Use when a user says "SDAF run failed", "my deploy exited non-zero", "the plan was clean but exit 1", "the run said success but nothing was deployed", "state lock error", "unexpected replacement", "control plane stopped partway", "generated hosSdaf Ha DiagnosticsDiagnose a live or recently failed SDAF high-availability cluster without changing cluster state. Start read-first: capture `crm status full` or `pcs status --full`, inspect SBD or fencing evidence, confirm current resource placement, and reuse existing quality-assurance or HCMT artifacts. Grounded in `docs/local/07-10-quality-assurance.md`, the shipped Pacemaker role vars/tasks, and the SAP Automation QA setup role. Use when a user says "diagnose my HANA failover", "crm status", "pcs status", "Sdaf Ha TopologyChoose the documented SDAF high-availability design before SAP-system deployment. Use when a user asks which HA topology to deploy, whether to use AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed, or which HA inputs must be set before deployment. Ground answers in the current support matrix, Ansible roles, sample tfvars, and validation logic. Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running the installers (sdaf-sap-installation).Sdaf Media AcquisitionAcquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Drives local `deploy/ansible/download_menu.sh` per `docs/local/06-00-software-and-installation.md § Download software`, enforces the documented `BOM_CATALOG` root and the four required `sap-parameters.yaml` BOM keys (`application_bom_name`, `database_bom_name`, `sap_kernel_bom_name`, `save_bom_as`), and explains the documented download and validation flow. Use for "download SAP media", "run download_menu.sh"