Skip to content

PTFE-3550: increase allowed tools with more readonly tools - #110

Closed
leif-scality wants to merge 1 commit into
mainfrom
improvement/PTFE-3550-add-read-tools-claude
Closed

leif-scality wants to merge 1 commit into
mainfrom
improvement/PTFE-3550-add-read-tools-claude

Conversation

@leif-scality

@leif-scality leif-scality commented Sep 22, 2026 •

Copy link
Copy Markdown

Increase readonly tools to improve reviews

@leif-scality
leif-scality requested a review from a team as a code owner September 22, 2026 11:19
@claude

claude Bot commented Sep 22, 2026

Copy link
Copy Markdown

LGTM

Review by Claude Code

@leif-scality
leif-scality force-pushed the improvement/PTFE-3550-add-read-tools-claude branch from 790ce60 to 363766e Compare September 22, 2026 11:29
@claude

claude Bot commented Sep 22, 2026

Copy link
Copy Markdown

LGTM

Review by Claude Code

@leif-scality leif-scality changed the title PTFE-3550: allow the gh reads a reviewer needs, and fall back on empty input PTFE-3550: increase allowed tools with more readonly tools Sep 22, 2026
@leif-scality
leif-scality force-pushed the improvement/PTFE-3550-add-read-tools-claude branch from 363766e to 33fe2d0 Compare September 22, 2026 12:31
@claude

claude Bot commented Sep 22, 2026

Copy link
Copy Markdown

LGTM

Review by Claude Code

contents: read
pull-requests: write
id-token: write # claude-code-action needs this to authenticate with GitHub
actions: read # `gh run view --log` reads the Actions API

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does it need to read the action log?
This is code review, not "fix CI build"

description: >
Space-separated list of allowed tools for the review. By default, a set of safe tools is allowed, but you can customize this list to enable or disable specific tools based on your needs and risk tolerance.
NOTE: should not be needed if the skill already indicates the appropriate allowed tools. Keeping default value for compatibility.
Space-separated list of allowed tools. Omit it to get the default below. A value passed

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need to add entries here?
This should not be needed, as indicated: it was kept only for compatibility with skills defined directly in each repo, and which did not have the proper permissions setup (in the skill)

Repos should use the generic/reusable review skill instead, and permissions must be added in that skill instead.

@leif-scality

Copy link
Copy Markdown
Author

@francoisferrand Closed this in favor of increasing the allowed tools in https://github.com/scality/agent-hub/pull/97. Also dropped the CI access, not much usefull info in it

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.

3 participants