Expand defineCliConfig to include adding CLI commands

[mikejarosch-aw]

Description

What is the appetite for expanding the defineCliConfig and sitecore-tools to additional commands. Right now, you can only add steps the project build command.

Proposal:

import * as sayHello from 'tools/commands/sayHello'; // Local command

export default defineCliConfig({
  commands: [sayHello],
  build: {
    ...
  },
});

You would then be able to execute this command like this: sitecore-tools sayHello

I would be happy to work on this and contribute, but don't want to waste my time if there is no interest.

Additional information

No response

[illiakovalenko]

Hey @mikejarosch-aw,
Sorry for the delayed response - just caught up with this thread.
It’s a reasonable idea and technically doable, but I’m not sure we need to extend sitecore.cli.config for it. The config is there to drive existing sitecore-tools commands (build steps, scaffold, component map). For custom or one-off automation that isn’t part of the SDK workflow, a separate npm script is usually enough - e.g. "my-command": "node tools/my-command.js" and then npm run my-command. That keeps the CLI focused and avoids the extra complexity of loading and registering config-based commands.
So for now I’d keep this out of scope. If we see strong demand or concrete use cases later, we can revisit.