Add CLAUDE.md for Claude Code onboarding (AST-146794)#1474
Add CLAUDE.md for Claude Code onboarding (AST-146794)#1474cx-anurag-dalke wants to merge 3 commits into
Conversation
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>
|
New Issues (1)Checkmarx found the following issues in this Pull Request
|
cx-atish-jadhav
left a comment
There was a problem hiding this comment.
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.
- 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>
Security Policy Alert: Secret Policy ViolationThis 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 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. |
Security Policy Alert: Secret Policy ViolationThis 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 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. |
Security Policy Alert: Secret Policy ViolationThis 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 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. |
Security Policy Alert: Secret Policy ViolationThis 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 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. |
Security Policy Alert: Runner Label Policy ViolationThis 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:
To fix this issue, please modify the For more information, see StepSecurity's Runner Label Policy documentation. |
Security Policy Alert: Runner Label Policy ViolationThis 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:
To fix this issue, please modify the For more information, see StepSecurity's Runner Label Policy documentation. |
1 similar comment
Security Policy Alert: Runner Label Policy ViolationThis 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:
To fix this issue, please modify the For more information, see StepSecurity's Runner Label Policy documentation. |
Security Policy Alert: Runner Label Policy ViolationThis 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:
To fix this issue, please modify the For more information, see StepSecurity's Runner Label Policy documentation. |


Summary
Test plan
Generated with Claude Code