Skip to content

Add CLAUDE.md for Claude Code onboarding (AST-146794)#1474

Open
cx-anurag-dalke wants to merge 3 commits into
mainfrom
feature/AST-146794
Open

Add CLAUDE.md for Claude Code onboarding (AST-146794)#1474
cx-anurag-dalke wants to merge 3 commits into
mainfrom
feature/AST-146794

Conversation

@cx-anurag-dalke
Copy link
Copy Markdown
Contributor

Summary

  • Adds comprehensive CLAUDE.md file to guide Claude Code when working in this repository
  • Covers project architecture (layered design, plugin ecosystem context), development setup (build, test, lint, coverage commands), testing strategy (unit/integration patterns, coverage thresholds, test file rules), deployment process, proxy configuration, debugging steps, and contributing guidelines
  • References internal Confluence documentation (Architecture Plugins, CLI Handover pages)

Test plan

  • Verify CLAUDE.md renders correctly on GitHub
  • Confirm all referenced file paths and commands are accurate
  • Validate Confluence links are accessible

Generated with Claude Code

Comprehensive guidance file covering project architecture, development
setup, testing strategy, deployment process, proxy configuration,
debugging steps, and contributing guidelines.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 15, 2026

Logo
Checkmarx One – Scan Summary & Details250104a8-289c-4ad5-b9a8-f2267436f3b9


New Issues (1) Checkmarx found the following issues in this Pull Request
# Severity Issue Source File / Package Checkmarx Insight
1 HIGH CVE-2026-35172 Go-github.com/distribution/distribution/v3-v3.0.1-0.20250403190400-dbca4995c83c
detailsDescription: Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after...
Attack Vector: NETWORK
Attack Complexity: LOW
Vulnerable Package

Copy link
Copy Markdown
Collaborator

@cx-atish-jadhav cx-atish-jadhav left a comment

Choose a reason for hiding this comment

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

Thanks for putting together this CLAUDE.md — it's well structured and covers all the sections required by the epic. Left a few inline remarks where the content drifts from what's actually in the repo today. Please verify and update before merging.

Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
Comment thread CLAUDE.md Outdated
- Fix --container-image flag to --container-images (matches params/flags.go)
- Update linter count from 19 to 20 (matches .golangci.yml linters.enable)
- Correct ci-tests.yml env var line range from 54-96 to 55-93
- Clarify lll setting is configured but not enabled/enforced
- Fix unit test coverage threshold from 85% to 77.7% (matches ci-tests.yml)
- Remove hardcoded internal hostname; reference CX_BASE_URI instead
- Replace non-existent pr-automation.yml with actual PR workflow files
- Replace non-existent update-trivy.yml with trivy-cache.yml; add missing
  workflows: ai-code-review.yml, dependabot-auto-merge.yml, nightly-parallel.yml

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Secret Policy Violation

This workflow run has been blocked by StepSecurity's secrets policy because it accesses secrets and the workflow file differs from the default branch.

To approve this workflow, please add the workflows-approved label to this PR.

Note: The label must be added by someone other than the PR author (cx-atish-jadhav) or automation bots to ensure proper security review.

After the label is added, you can re-run the blocked workflow to proceed.

This workflow will be automatically approved once merged into the default branch.

For more information, see StepSecurity's Secret Exfiltration Policy documentation.

@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Secret Policy Violation

This workflow run has been blocked by StepSecurity's secrets policy because it accesses secrets and the workflow file differs from the default branch.

To approve this workflow, please add the workflows-approved label to this PR.

Note: The label must be added by someone other than the PR author (cx-atish-jadhav) or automation bots to ensure proper security review.

After the label is added, you can re-run the blocked workflow to proceed.

This workflow will be automatically approved once merged into the default branch.

For more information, see StepSecurity's Secret Exfiltration Policy documentation.

@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Secret Policy Violation

This workflow run has been blocked by StepSecurity's secrets policy because it accesses secrets and the workflow file differs from the default branch.

To approve this workflow, please add the workflows-approved label to this PR.

Note: The label must be added by someone other than the PR author (cx-atish-jadhav) or automation bots to ensure proper security review.

After the label is added, you can re-run the blocked workflow to proceed.

This workflow will be automatically approved once merged into the default branch.

For more information, see StepSecurity's Secret Exfiltration Policy documentation.

@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Secret Policy Violation

This workflow run has been blocked by StepSecurity's secrets policy because it accesses secrets and the workflow file differs from the default branch.

To approve this workflow, please add the workflows-approved label to this PR.

Note: The label must be added by someone other than the PR author (cx-atish-jadhav) or automation bots to ensure proper security review.

After the label is added, you can re-run the blocked workflow to proceed.

This workflow will be automatically approved once merged into the default branch.

For more information, see StepSecurity's Secret Exfiltration Policy documentation.

@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Runner Label Policy Violation

This workflow run has been blocked by StepSecurity's runner label policy because it uses runner labels that are not allowed by your organization's policy.

Disallowed Runner Labels:

  • ubuntu-latest

To fix this issue, please modify the runs-on field in your workflow to use only allowed runner labels. Contact your organization administrator if you need further assistance.

For more information, see StepSecurity's Runner Label Policy documentation.

@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Runner Label Policy Violation

This workflow run has been blocked by StepSecurity's runner label policy because it uses runner labels that are not allowed by your organization's policy.

Disallowed Runner Labels:

  • ubuntu-latest

To fix this issue, please modify the runs-on field in your workflow to use only allowed runner labels. Contact your organization administrator if you need further assistance.

For more information, see StepSecurity's Runner Label Policy documentation.

1 similar comment
@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Runner Label Policy Violation

This workflow run has been blocked by StepSecurity's runner label policy because it uses runner labels that are not allowed by your organization's policy.

Disallowed Runner Labels:

  • ubuntu-latest

To fix this issue, please modify the runs-on field in your workflow to use only allowed runner labels. Contact your organization administrator if you need further assistance.

For more information, see StepSecurity's Runner Label Policy documentation.

@stepsecurity-app
Copy link
Copy Markdown
Contributor

Security Policy Alert: Runner Label Policy Violation

This workflow run has been blocked by StepSecurity's runner label policy because it uses runner labels that are not allowed by your organization's policy.

Disallowed Runner Labels:

  • ubuntu-latest

To fix this issue, please modify the runs-on field in your workflow to use only allowed runner labels. Contact your organization administrator if you need further assistance.

For more information, see StepSecurity's Runner Label Policy documentation.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants