Skip to content

feat: register the snyk agent (AXI) extension#6954

Draft
mattdolan-snyk wants to merge 1 commit into
snyk:mainfrom
mattdolan-snyk:feat/agent-extension
Draft

feat: register the snyk agent (AXI) extension#6954
mattdolan-snyk wants to merge 1 commit into
snyk:mainfrom
mattdolan-snyk:feat/agent-extension

Conversation

@mattdolan-snyk

Copy link
Copy Markdown

Wire github.com/snyk-playground/cli-extension-axi into the CLI:

  • initExtensions registers agent.Init, adding the snyk agent command surface (agent-ergonomic, TOON output): agent, agent test [scanners...], agent context, agent setup hooks.
  • createCommandsForWorkflows sets a help func on the agent command (inherited by the subtree) that delegates to agent.RenderHelp with the engine, so the extension can render per-command help by introspecting each scanner's underlying workflow flags — without hardcoding other extensions' flags.

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

Wire github.com/snyk-playground/cli-extension-axi into the CLI:

- initExtensions registers agent.Init, adding the `snyk agent` command surface
  (agent-ergonomic, TOON output): `agent`, `agent test [scanners...]`,
  `agent context`, `agent setup hooks`.
- createCommandsForWorkflows sets a help func on the `agent` command (inherited
  by the subtree) that delegates to agent.RenderHelp with the engine, so the
  extension can render per-command help by introspecting each scanner's
  underlying workflow flags — without hardcoding other extensions' flags.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@snyk-io

snyk-io Bot commented Jun 26, 2026

Copy link
Copy Markdown

⚠️ Snyk checks are incomplete.

Status Scan Engine Critical High Medium Low Total (0)
⚠️ Open Source Security 0 0 0 0 See details
⚠️ Licenses 0 0 0 0 See details
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants