docs: atl security-level flag + read-only api passthrough#107
Merged
Conversation
Document the atl-cli additions from enthus-appdev/atl-cli#65: - create/edit --security "<name|id>" (and --security "" to clear on edit) - field-options surfaces the project's security levels - atl jira api [GET] <path> read-only REST passthrough - --field-file table points the securitylevel type at --security Gated on atl-cli#65 merging and an atl release that ships these commands — do not merge until an installed atl has them. Claude-Session: https://claude.ai/code/session_017itWrHCyk9EQRViji4QY3G
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation in lib/llm/index.js to include examples and explanations for the new --security flag used in creating and editing Jira issues, as well as discovering security levels via field-options. It also documents the read-only REST API passthrough command (atl jira api). There are no review comments to address, and I have no additional feedback to provide.
Hinne1
marked this pull request as ready for review
July 22, 2026 05:37
The publish workflow fires on release and ships package.json's version, so the doc change needs a version bump to reach devs. Mark the new --security and api-passthrough docs as atl v1.12.0+ (now released). Claude-Session: https://claude.ai/code/session_017itWrHCyk9EQRViji4QY3G
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the atl-cli additions from enthus-appdev/atl-cli#65 in the injected
cli-atlreference (lib/llm/index.js):create/edit --security "<name|id>"(and--security ""to clear on edit)field-options ... --field securitysurfaces the project's security levelsatl jira api [GET] <path>read-only REST passthrough--fieldvs--field-filetable points thesecurityleveltype at the new--securityflag (it can't be set via--field)These docs describe commands that only exist once atl-cli#65 merges and an
atlrelease ships them. Merging this before then would inject docs for commands the installedatldoesn't have. Gate: atl-cli#65 merged → atl released → then mark ready.Checks
node --check lib/llm/index.js— syntax OKnpm run lint(eslint) — cleannpm run check-format(prettier) — cleanhttps://claude.ai/code/session_017itWrHCyk9EQRViji4QY3G