Skip to content

chore(standards): synced file(s) with hallelx2/dev-standards - #4

Open
hallelx2 wants to merge 10 commits into
mainfrom
repo-sync/dev-standards/default
Open

chore(standards): synced file(s) with hallelx2/dev-standards#4
hallelx2 wants to merge 10 commits into
mainfrom
repo-sync/dev-standards/default

Conversation

@hallelx2

@hallelx2 hallelx2 commented Jun 13, 2026

Copy link
Copy Markdown
Owner

synced local file(s) with hallelx2/dev-standards.

Changed files
  • created local AGENTS.md from remote AGENTS.md
  • created local .github/copilot-instructions.md from remote .github/copilot-instructions.md
  • created local directory .github/agents/ and copied all sub files/folders from remote directory .github/agents/
  • created local .github/instructions/backend.instructions.md from remote .github/instructions/backend.instructions.md
  • created local .github/instructions/frontend.instructions.md from remote .github/instructions/frontend.instructions.md
  • created local .github/instructions/security.instructions.md from remote .github/instructions/security.instructions.md
  • created local .github/workflows/security.yml from remote .github/workflows/security.yml
  • created local .github/workflows/security.reusable.yml from remote .github/workflows/security.reusable.yml
  • created local .github/workflows/jules-review.yml from remote .github/workflows/jules-review.yml
  • created local .github/dependabot.yml from remote .github/dependabot.yml

This PR was created automatically by the repo-file-sync-action workflow run #30801469164

Summary by CodeRabbit

  • New Features

    • Added automated pull request security reviews and reusable security scanning workflows.
    • Added specialized review guidance for backend, frontend, security, and test reliability checks.
    • Added shared engineering standards for AI-assisted development and code reviews.
  • Chores

    • Added automated dependency update configuration with scheduled package and action updates.

Copilot AI review requested due to automatic review settings June 13, 2026 02:11
@vercel

vercel Bot commented Jun 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
vectorless-docs Error Error Aug 3, 2026 9:28am

@sourcery-ai

sourcery-ai Bot commented Jun 13, 2026

Copy link
Copy Markdown

Reviewer's Guide

Adds synced dev-standards documentation, AI reviewer agent configs, path-scoped review instructions, and reusable security/Jules review GitHub Actions workflows to align this repo with the centralized dev-standards configuration.

Sequence diagram for jules-review GitHub Action execution

sequenceDiagram
  actor Dev
  participant Repo
  participant GitHub_Actions
  participant Jules_Workflow as jules-review
  participant Guard_Step as guard
  participant Jules_Action as sanjay3290/jules-pr-reviewer

  Dev->>Repo: open/synchronize PR
  Repo->>GitHub_Actions: pull_request event
  GitHub_Actions->>Jules_Workflow: start workflow
  Jules_Workflow->>Guard_Step: run guard step
  alt JULES_API_KEY set
    Guard_Step-->>Jules_Workflow: enabled=true
    Jules_Workflow->>Jules_Action: run jules-pr-reviewer
  else JULES_API_KEY not set
    Guard_Step-->>Jules_Workflow: enabled=false
    Jules_Workflow-->>Dev: log skip message
  end
Loading

File-Level Changes

Change Details Files
Introduce central AGENTS brief and Copilot review baseline for all AI-assisted reviews.
  • Add AGENTS.md describing repo-wide AI agent expectations, workflow, conventions, and security focus areas.
  • Add .github/copilot-instructions.md to define Copilot’s PR review rubric (right thing, done right, safe).
AGENTS.md
.github/copilot-instructions.md
Add specialized AI agent configs for backend, frontend, security, and test-reliability review.
  • Define backend-reviewer.agent.md with Go-focused correctness/concurrency/error-handling rubric.
  • Define frontend-reviewer.agent.md with Next/TypeScript, XSS, accessibility, and performance rubric.
  • Define security-reviewer.agent.md emphasizing auth, multi-tenant isolation, BYOK, injection, and crypto.
  • Define test-reliability-reviewer.agent.md for test coverage, determinism, and reliability checks.
.github/agents/backend-reviewer.agent.md
.github/agents/frontend-reviewer.agent.md
.github/agents/security-reviewer.agent.md
.github/agents/test-reliability-reviewer.agent.md
Configure path-scoped review instructions to automatically guide AI reviewers per file type and globally for security.
  • Add backend.instructions.md applying Go review rules to **/*.go files.
  • Add frontend.instructions.md applying frontend review rules to TS/TSX/CSS files.
  • Add security.instructions.md applying security review checks to all files in the repo.
.github/instructions/backend.instructions.md
.github/instructions/frontend.instructions.md
.github/instructions/security.instructions.md
Add reusable security scanning workflow and caller workflow to standardize CI security checks.
  • Introduce security.reusable.yml reusable workflow running gitleaks, Trivy (vuln/secret/misconfig), and conditional gosec SAST.
  • Add security.yml workflow that triggers on PRs and main pushes and calls the reusable security workflow with inherited secrets.
.github/workflows/security.reusable.yml
.github/workflows/security.yml
Add optional Jules-based automated security review on PRs gated by presence of JULES_API_KEY secret.
  • Create jules-review.yml workflow that runs on PR events, checks for JULES_API_KEY, and invokes sanjay3290/jules-pr-reviewer when enabled.
  • Configure review-prompt to align Jules with security-reviewer.agent.md, focusing on auth, multi-tenant leakage, BYOK, injection/SSRF, and crypto issues.
.github/workflows/jules-review.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Repository review standards, specialized agent instructions, Dependabot configuration, and reusable security workflows were added. Automation covers pull-request security reviews, secret scanning, SAST, vulnerability checks, and filesystem scanning.

Changes

Review and Security Standards

Layer / File(s) Summary
Shared review policy
AGENTS.md, .github/copilot-instructions.md
Defines repository-wide engineering, acceptance-criteria, correctness, testing, security, and language-specific review guidance.
Specialized reviewer guidance
.github/agents/*, .github/instructions/*
Adds backend, frontend, security, and test-reliability review prompts and path-scoped checklists with citation and finding requirements.
Security automation and dependency updates
.github/dependabot.yml, .github/workflows/*
Configures weekly dependency updates, Jules pull-request reviews, reusable security scanners, and pull-request/main-branch workflow wiring.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies an automated standards synchronization, which matches the pull request’s primary change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch repo-sync/dev-standards/default

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • In .github/workflows/security.reusable.yml, consider pinning third-party actions like aquasecurity/trivy-action@0.28.0 and gitleaks/gitleaks-action@v2 to specific commit SHAs rather than tags to reduce supply-chain risk from upstream tag moves.
  • In .github/workflows/jules-review.yml, you may want to restrict the trigger (e.g., pull_request types or paths) if you expect Jules to run only on certain PRs, to avoid unnecessary runs/noise on trivial or non-code changes.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In `.github/workflows/security.reusable.yml`, consider pinning third-party actions like `aquasecurity/trivy-action@0.28.0` and `gitleaks/gitleaks-action@v2` to specific commit SHAs rather than tags to reduce supply-chain risk from upstream tag moves.
- In `.github/workflows/jules-review.yml`, you may want to restrict the trigger (e.g., `pull_request` types or paths) if you expect Jules to run only on certain PRs, to avoid unnecessary runs/noise on trivial or non-code changes.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR syncs shared engineering/AI-agent standards and security-related GitHub Actions workflows from hallelx2/dev-standards into vectorless-docs to standardize review guidance and baseline security scanning across repositories.

Changes:

  • Add AGENTS.md plus Copilot/agent instruction files to standardize AI-assisted review expectations (backend/frontend/security/test reliability).
  • Add path-scoped review rubrics under .github/instructions/ to auto-apply guidance by file type.
  • Add security scanning workflows (gitleaks/Trivy/gosec) and an optional Jules-based PR security review workflow.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
AGENTS.md Adds shared engineering/review standards and Vectorless-specific security priorities.
.github/copilot-instructions.md Defines baseline Copilot PR review rubric (right thing / done right / safe).
.github/agents/backend-reviewer.agent.md Adds a specialized Go backend review agent prompt.
.github/agents/frontend-reviewer.agent.md Adds a specialized Next.js/TypeScript review agent prompt.
.github/agents/security-reviewer.agent.md Adds an adversarial security review agent prompt focused on OWASP + multi-tenant/BYOK.
.github/agents/test-reliability-reviewer.agent.md Adds a test reliability agent prompt focusing on determinism and proof of behavior.
.github/instructions/backend.instructions.md Path-scoped Go review rubric (**/*.go).
.github/instructions/frontend.instructions.md Path-scoped TS/TSX/CSS review rubric (frontend focus).
.github/instructions/security.instructions.md Global security review rubric applied to all changes.
.github/workflows/security.yml Adds caller workflow to run the reusable security scanners on PRs and main pushes.
.github/workflows/security.reusable.yml Adds reusable security scanners (gitleaks, Trivy FS scan, conditional gosec).
.github/workflows/jules-review.yml Adds optional automated Jules security review workflow gated by JULES_API_KEY.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +21 to +22
uses: ./.github/workflows/security.reusable.yml
secrets: inherit
Comment on lines +52 to +56
- name: gosec
if: steps.detect.outputs.is_go == 'true'
uses: securego/gosec@master
with:
args: -no-fail -fmt text ./...
Comment thread .github/workflows/jules-review.yml Outdated
Comment on lines +21 to +32
- name: Guard — only run when a Jules key is configured
id: guard
run: |
if [ -n "${{ secrets.JULES_API_KEY }}" ]; then
echo "enabled=true" >> "$GITHUB_OUTPUT"
else
echo "enabled=false" >> "$GITHUB_OUTPUT"
echo "No JULES_API_KEY set — skipping automated Jules review. Use @jules on the PR instead."
fi
- name: Jules security review
if: steps.guard.outputs.enabled == 'true'
uses: sanjay3290/jules-pr-reviewer@main
Comment on lines +30 to +35
- name: Jules security review
if: steps.guard.outputs.enabled == 'true'
uses: sanjay3290/jules-pr-reviewer@main
with:
jules-api-key: ${{ secrets.JULES_API_KEY }}
github-token: ${{ github.token }}
Comment on lines +1 to +3
---
applyTo: "**/*.ts,**/*.tsx,**/*.css"
---
@hallelx2
hallelx2 force-pushed the repo-sync/dev-standards/default branch from 54520f6 to 7cdd707 Compare June 13, 2026 02:13
@hallelx2
hallelx2 force-pushed the repo-sync/dev-standards/default branch from 7cdd707 to 3a777e0 Compare June 13, 2026 02:20
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

# Local reference — the reusable file is synced into THIS repo too, so each repo
# is self-contained and this works whether dev-standards is public or private.
uses: ./.github/workflows/security.reusable.yml
secrets: inherit
steps:
- uses: actions/checkout@v4
- name: Install Trivy (latest binary — avoids the action's broken setup-trivy pin)
run: curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
name: Vulns + misconfig (Trivy)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
id: detect
run: |
if ls requirements*.txt pyproject.toml setup.py >/dev/null 2>&1; then echo "is_py=true" >> "$GITHUB_OUTPUT"; else echo "is_py=false" >> "$GITHUB_OUTPUT"; fi
- uses: actions/setup-python@v5
name: Python deps + SAST (pip-audit + bandit)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: gitleaks/gitleaks-action@v2
name: Secrets (gitleaks)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
Comment thread .github/dependabot.yml
Comment on lines +19 to +24
- package-ecosystem: npm
directory: "/"
schedule:
interval: weekly
open-pull-requests-limit: 5
labels: [dependencies, security]
Comment thread .github/dependabot.yml
Comment on lines +12 to +17
- package-ecosystem: gomod
directory: "/"
schedule:
interval: weekly
open-pull-requests-limit: 5
labels: [dependencies, security]
Comment thread .github/dependabot.yml
Comment on lines +6 to +10
- package-ecosystem: github-actions
directory: "/"
schedule:
interval: weekly
labels: [dependencies, security]

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (2)
.github/workflows/jules-review.yml (1)

24-28: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Pass JULES_API_KEY via env instead of interpolating into the shell script.

${{ secrets.JULES_API_KEY }} is interpolated directly into the script text before the shell executes. If the secret contains shell metacharacters (", $, backticks), the script can break or behave unexpectedly. Use an environment variable to keep the value out of the script body.

Proposed fix
       - name: Guard — only run when a Jules key is configured
         id: guard
+        env:
+          JULES_API_KEY: ${{ secrets.JULES_API_KEY }}
         run: |
-          if [ -n "${{ secrets.JULES_API_KEY }}" ]; then
+          if [ -n "$JULES_API_KEY" ]; then
             echo "enabled=true" >> "$GITHUB_OUTPUT"
           else
             echo "enabled=false" >> "$GITHUB_OUTPUT"
             echo "No JULES_API_KEY set — skipping automated Jules review. Use `@jules` on the PR instead."
           fi
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/jules-review.yml around lines 24 - 28, Update the Jules
API key check in the workflow step to read JULES_API_KEY from the step
environment rather than interpolating secrets.JULES_API_KEY directly into the
shell script. Preserve the existing enabled/disabled outputs and skip message
while configuring the environment mapping for the secret.
.github/workflows/security.reusable.yml (1)

22-24: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Set persist-credentials: false on all checkout steps.

actions/checkout persists the GitHub token in .git/config by default. If a compromised scanner reads the workspace, it can extract the token. No subsequent step in any job needs git credentials, so persist-credentials: false is safe.

Proposed fix

For the secret-scan job (which also sets fetch-depth: 0):

       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
+          persist-credentials: false

For all other checkout steps (no existing with block):

-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false

Also applies to: 35-35, 58-58, 77-77, 92-92, 111-111, 131-131

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/security.reusable.yml around lines 22 - 24, Update every
actions/checkout@v4 step in the workflow, including the secret-scan checkout
with fetch-depth: 0, to set persist-credentials to false in its with block.
Preserve each checkout’s existing options and add the setting to all referenced
checkout steps.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/security.reusable.yml:
- Line 33: Pin the Semgrep container image in the workflow’s image configuration
to an explicit immutable version tag or, preferably, a digest instead of the
floating semgrep/semgrep default. Preserve the existing Semgrep execution
behavior while ensuring every CI run uses the same trusted image.

In `@AGENTS.md`:
- Line 12: Update the validation guidance in AGENTS.md so the “Done” requirement
explicitly includes repository-appropriate build, test, and lint commands, not
typechecking alone. Extend the Go commands to include go test -race where
applicable, and add explicit TypeScript test and lint commands alongside the
existing build examples.

---

Nitpick comments:
In @.github/workflows/jules-review.yml:
- Around line 24-28: Update the Jules API key check in the workflow step to read
JULES_API_KEY from the step environment rather than interpolating
secrets.JULES_API_KEY directly into the shell script. Preserve the existing
enabled/disabled outputs and skip message while configuring the environment
mapping for the secret.

In @.github/workflows/security.reusable.yml:
- Around line 22-24: Update every actions/checkout@v4 step in the workflow,
including the secret-scan checkout with fetch-depth: 0, to set
persist-credentials to false in its with block. Preserve each checkout’s
existing options and add the setting to all referenced checkout steps.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9dddf1c9-6918-4666-9942-01668aaf0b03

📥 Commits

Reviewing files that changed from the base of the PR and between 8eee521 and 3b137f7.

📒 Files selected for processing (13)
  • .github/agents/backend-reviewer.agent.md
  • .github/agents/frontend-reviewer.agent.md
  • .github/agents/security-reviewer.agent.md
  • .github/agents/test-reliability-reviewer.agent.md
  • .github/copilot-instructions.md
  • .github/dependabot.yml
  • .github/instructions/backend.instructions.md
  • .github/instructions/frontend.instructions.md
  • .github/instructions/security.instructions.md
  • .github/workflows/jules-review.yml
  • .github/workflows/security.reusable.yml
  • .github/workflows/security.yml
  • AGENTS.md

name: SAST — OWASP Top 10 + CWE Top 25 (Semgrep)
runs-on: ubuntu-latest
container:
image: semgrep/semgrep

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Pin the Semgrep container image to a specific version or digest.

image: semgrep/semgrep pulls the latest tag by default. If a compromised or broken image is pushed, it affects every CI run that uses this workflow. Pin to a specific version tag or, ideally, a digest.

Proposed fix
     container:
-      image: semgrep/semgrep
+      image: semgrep/semgrep:1.75.0

Or pin by digest for maximum reproducibility:

     container:
-      image: semgrep/semgrep
+      image: semgrep/semgrep@sha256:<digest>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
image: semgrep/semgrep
image: semgrep/semgrep:1.75.0
🧰 Tools
🪛 zizmor (1.26.1)

[error] 33-33: unpinned image references (unpinned-images): container image is unpinned

(unpinned-images)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/security.reusable.yml at line 33, Pin the Semgrep
container image in the workflow’s image configuration to an explicit immutable
version tag or, preferably, a digest instead of the floating semgrep/semgrep
default. Preserve the existing Semgrep execution behavior while ensuring every
CI run uses the same trusted image.

Source: Linters/SAST tools

Comment thread AGENTS.md
- **One issue → one branch → one PR → one outcome.** Use the Linear branch name (`halleluyaholudele/hal-<n>-<title>`). Never commit to `main` directly.
- Put **`Closes HAL-<n>`** in the **PR description** so Linear links + auto-closes on merge.
- **No AI attribution** in commits, PRs, or any artifact. Author as the user alone.
- "Done" = real build + tests + lint pass (run them — `go build ./... && go test ./...`, `bun run build` / `npm run build`), not just typecheck.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Make the required validation commands complete.

Line 12 requires build, tests, and lint, but the examples show only build for TypeScript and omit go test -race, despite the Go concurrency requirement on Line 24. Add explicit repository-appropriate test/lint commands and the race check where applicable.

Based on learnings: a change is done only after the real build, tests, and lint pass; do not rely on typechecking alone.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@AGENTS.md` at line 12, Update the validation guidance in AGENTS.md so the
“Done” requirement explicitly includes repository-appropriate build, test, and
lint commands, not typechecking alone. Extend the Go commands to include go test
-race where applicable, and add explicit TypeScript test and lint commands
alongside the existing build examples.

Source: Learnings

hallelx2 added 10 commits August 3, 2026 09:27
Synced AI-review standards from hallelx2/dev-standards.
…m remote '.github/copilot-instructions.md'

Synced AI-review standards from hallelx2/dev-standards.
…b/agents/'

Synced AI-review standards from hallelx2/dev-standards.
…tions.md' from remote '.github/instructions/backend.instructions.md'

Synced AI-review standards from hallelx2/dev-standards.
…ctions.md' from remote '.github/instructions/frontend.instructions.md'

Synced AI-review standards from hallelx2/dev-standards.
…ctions.md' from remote '.github/instructions/security.instructions.md'

Synced AI-review standards from hallelx2/dev-standards.
… remote '.github/workflows/security.yml'

Synced AI-review standards from hallelx2/dev-standards.
…yml' from remote '.github/workflows/security.reusable.yml'

Synced AI-review standards from hallelx2/dev-standards.
…from remote '.github/workflows/jules-review.yml'

Synced AI-review standards from hallelx2/dev-standards.
…'.github/dependabot.yml'

Synced AI-review standards from hallelx2/dev-standards.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/security.reusable.yml:
- Around line 37-52: Update .github/workflows/security.reusable.yml lines 37-52
to remove Semgrep’s error-swallowing behavior and make SARIF upload failures
fail the job; preserve govulncheck failures at lines 69-71, define an explicit
failure policy for gosec at lines 82-86, preserve npm audit failures at lines
103-105 and pip-audit/Bandit failures at lines 120-125, and make high/critical
Trivy findings actionable at lines 132-135. Do not weaken any scanner or upload
failure controls.
- Around line 22-24: Disable persisted checkout credentials by setting
persist-credentials to false on every actions/checkout step in
.github/workflows/security.reusable.yml: lines 22-24 (secret-scan), 35
(sast-semgrep), 58 (go-cves), 77 (go-sast), 92 (node-cves), 111 (python-sast),
and 131 (infra-trivy).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bfed3064-4acb-4abb-82ff-4a5644537f7e

📥 Commits

Reviewing files that changed from the base of the PR and between 3b137f7 and e6ea92b.

📒 Files selected for processing (13)
  • .github/agents/backend-reviewer.agent.md
  • .github/agents/frontend-reviewer.agent.md
  • .github/agents/security-reviewer.agent.md
  • .github/agents/test-reliability-reviewer.agent.md
  • .github/copilot-instructions.md
  • .github/dependabot.yml
  • .github/instructions/backend.instructions.md
  • .github/instructions/frontend.instructions.md
  • .github/instructions/security.instructions.md
  • .github/workflows/jules-review.yml
  • .github/workflows/security.reusable.yml
  • .github/workflows/security.yml
  • AGENTS.md
🚧 Files skipped from review as they are similar to previous changes (8)
  • .github/agents/backend-reviewer.agent.md
  • .github/agents/frontend-reviewer.agent.md
  • .github/agents/security-reviewer.agent.md
  • .github/instructions/backend.instructions.md
  • .github/instructions/frontend.instructions.md
  • .github/agents/test-reliability-reviewer.agent.md
  • .github/instructions/security.instructions.md
  • .github/workflows/jules-review.yml

Comment on lines +22 to +24
- uses: actions/checkout@v4
with:
fetch-depth: 0

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail
rg -n -A3 -B1 'uses:\s*actions/checkout@|persist-credentials:' .github/workflows/security.reusable.yml

Repository: hallelx2/vectorless-docs

Length of output: 1300


🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail
cat -n .github/workflows/security.reusable.yml | sed -n '1,155p'

Repository: hallelx2/vectorless-docs

Length of output: 5981


Disable persisted checkout credentials.

actions/checkout@v4 persists the GitHub token in the local Git config by default. Set persist-credentials: false on every checkout before later installers can access those credentials.

  • .github/workflows/security.reusable.yml#L22-L24: disable credential persistence for secret-scan.
  • .github/workflows/security.reusable.yml#L35-L35: disable credential persistence for sast-semgrep.
  • .github/workflows/security.reusable.yml#L58-L58: disable credential persistence for go-cves.
  • .github/workflows/security.reusable.yml#L77-L77: disable credential persistence for go-sast.
  • .github/workflows/security.reusable.yml#L92-L92: disable credential persistence for node-cves.
  • .github/workflows/security.reusable.yml#L111-L111: disable credential persistence for python-sast.
  • .github/workflows/security.reusable.yml#L131-L131: disable credential persistence for infra-trivy.
🧰 Tools
🪛 GitHub Check: Semgrep OSS

[warning] 22-22: Semgrep Finding: yaml.github-actions.security.github-actions-mutable-action-tag.github-actions-mutable-action-tag
GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608.

🪛 zizmor (1.28.0)

[warning] 22-24: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

📍 Affects 1 file
  • .github/workflows/security.reusable.yml#L22-L24 (this comment)
  • .github/workflows/security.reusable.yml#L35-L35
  • .github/workflows/security.reusable.yml#L58-L58
  • .github/workflows/security.reusable.yml#L77-L77
  • .github/workflows/security.reusable.yml#L92-L92
  • .github/workflows/security.reusable.yml#L111-L111
  • .github/workflows/security.reusable.yml#L131-L131
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/security.reusable.yml around lines 22 - 24, Disable
persisted checkout credentials by setting persist-credentials to false on every
actions/checkout step in .github/workflows/security.reusable.yml: lines 22-24
(secret-scan), 35 (sast-semgrep), 58 (go-cves), 77 (go-sast), 92 (node-cves),
111 (python-sast), and 131 (infra-trivy).

Sources: Coding guidelines, Linters/SAST tools

Comment on lines +37 to +52
run: |
semgrep scan \
--config p/owasp-top-ten \
--config p/cwe-top-25 \
--config p/secrets \
--config p/javascript \
--config p/typescript \
--config p/python \
--config p/github-actions \
--sarif --output semgrep.sarif || true
- name: Upload Semgrep SARIF
if: always()
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: semgrep.sarif
continue-on-error: true

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Fail when a security scanner cannot produce a reliable result.

|| true, continue-on-error: true, -no-fail, and --exit-code 0 allow this workflow to complete successfully after scanner failures or confirmed findings. Keep advisory findings separate if needed, but fail the job when a scanner cannot run or upload its result.

  • .github/workflows/security.reusable.yml#L37-L52: preserve Semgrep and SARIF upload failures.
  • .github/workflows/security.reusable.yml#L69-L71: preserve govulncheck failures.
  • .github/workflows/security.reusable.yml#L82-L86: define an explicit failure policy for gosec.
  • .github/workflows/security.reusable.yml#L103-L105: preserve npm audit failures.
  • .github/workflows/security.reusable.yml#L120-L125: preserve pip-audit and Bandit failures.
  • .github/workflows/security.reusable.yml#L132-L135: make high and critical Trivy findings actionable.

As per coding guidelines, do not weaken security controls by swallowing errors.

🧰 Tools
🪛 GitHub Check: Semgrep OSS

[warning] 49-49: Semgrep Finding: yaml.github-actions.security.github-actions-mutable-action-tag.github-actions-mutable-action-tag
GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608.

📍 Affects 1 file
  • .github/workflows/security.reusable.yml#L37-L52 (this comment)
  • .github/workflows/security.reusable.yml#L69-L71
  • .github/workflows/security.reusable.yml#L82-L86
  • .github/workflows/security.reusable.yml#L103-L105
  • .github/workflows/security.reusable.yml#L120-L125
  • .github/workflows/security.reusable.yml#L132-L135
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/security.reusable.yml around lines 37 - 52, Update
.github/workflows/security.reusable.yml lines 37-52 to remove Semgrep’s
error-swallowing behavior and make SARIF upload failures fail the job; preserve
govulncheck failures at lines 69-71, define an explicit failure policy for gosec
at lines 82-86, preserve npm audit failures at lines 103-105 and
pip-audit/Bandit failures at lines 120-125, and make high/critical Trivy
findings actionable at lines 132-135. Do not weaken any scanner or upload
failure controls.

Source: Coding guidelines

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants