Person
Jan Ježek
Capabilities
Contributes to
Clean code conventionsABAPClean code conventionsThe naming, structure and language-subset conventions that make source code readable across a team — and the question of which of them a checker can enforce.Source controlABAPSource controlKeeping source code and development objects in version control, comparing their revisions, and moving them between development environments. Managed delivery of changes belongs to [transport management](capability:change-promotion).Static analysisABAPStatic analysisCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.
Entries
Group by
EntrySignals
Contributes to
abapGitabapGitA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap
Git client written in ABAP that runs inside the system
abaplintabaplintStatic analysis for ABAP that runs outside a system on serialised source in a repository, so ABAP checks run in a pull request and in CI before the code ever reaches a system.community org, abap
Static analysis for ABAP source outside a system
Clean ABAPClean ABAPSAP's open, versioned style guide for ABAP: the answer to how a piece of ABAP should be written, an agreement a team adopts rather than anything to install.sap official, abap
Open, versioned style guide for ABAP
Details
For your agent
- Ref
actor:jan-jezek- JSON
- /actors/jan-jezek.json
- MCP
- Connecting an agent