<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: brunnodev</title>
    <description>The latest articles on DEV Community by brunnodev (@brunnojob).</description>
    <link>https://dev.to/brunnojob</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4196891%2F891b83c7-1f5e-4510-8954-60b8ff50407c.png</url>
      <title>DEV Community: brunnodev</title>
      <link>https://dev.to/brunnojob</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/brunnojob"/>
    <language>en</language>
    <item>
      <title>Review risky pull request changes without AI keys: meet PatchScope</title>
      <dc:creator>brunnodev</dc:creator>
      <pubDate>Wed, 18 Nov 2026 04:00:48 +0000</pubDate>
      <link>https://dev.to/brunnojob/review-risky-pull-request-changes-without-ai-keys-meet-patchscope-30jj</link>
      <guid>https://dev.to/brunnojob/review-risky-pull-request-changes-without-ai-keys-meet-patchscope-30jj</guid>
      <description>&lt;p&gt;`A pull request can pass its tests and still remove useful coverage, broaden workflow permissions or introduce destructive SQL.&lt;/p&gt;

&lt;p&gt;I built &lt;strong&gt;PatchScope&lt;/strong&gt; to help reviewers find those changes and decide what to inspect next.&lt;/p&gt;

&lt;p&gt;It turns a Git diff into an actionable review checklist, with an explanation of what matched, why it matters and what to check.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/marketplace/actions/patchscope-diff-review" rel="noopener noreferrer"&gt;Install from GitHub Marketplace&lt;/a&gt;&lt;/strong&gt; · &lt;strong&gt;&lt;a href="https://brunnojob.github.io/patchscope/" rel="noopener noreferrer"&gt;Try the browser demo&lt;/a&gt;&lt;/strong&gt; · &lt;strong&gt;&lt;a href="https://github.com/brunnojob/patchscope" rel="noopener noreferrer"&gt;Source code&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqsrz6ifr5wpqey5jkww7.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqsrz6ifr5wpqey5jkww7.jpg" alt="PatchScope interface showing a diff and its review checklist" width="800" height="550"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What does it look for?
&lt;/h2&gt;

&lt;p&gt;PatchScope uses deterministic rules to identify review signals such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Removed test files.&lt;/li&gt;
&lt;li&gt;Skipped or exclusive tests.&lt;/li&gt;
&lt;li&gt;Broad GitHub Actions permissions.&lt;/li&gt;
&lt;li&gt;Potentially destructive SQL.&lt;/li&gt;
&lt;li&gt;Dependency changes that deserve a reproducibility check.&lt;/li&gt;
&lt;li&gt;Known TLS verification bypass patterns.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each finding becomes a concrete review prompt.&lt;/p&gt;

&lt;p&gt;These are &lt;strong&gt;heuristics for human review&lt;/strong&gt;, not confirmed vulnerabilities. A match can be intentional, and an empty report does not establish that a patch is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  One engine, three ways to use it
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Environment&lt;/th&gt;
&lt;th&gt;What you get&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Browser&lt;/td&gt;
&lt;td&gt;Interactive diff exploration and a review checklist&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CLI&lt;/td&gt;
&lt;td&gt;Markdown, JSON or SARIF reports&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GitHub Actions&lt;/td&gt;
&lt;td&gt;A job summary and report files for your workflow&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;No AI API keys, model subscription or application account is required. Analysis runs locally in the browser, terminal or CI runner.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it before installing
&lt;/h2&gt;

&lt;p&gt;Open the &lt;a href="https://brunnojob.github.io/patchscope/" rel="noopener noreferrer"&gt;browser demo&lt;/a&gt; and click &lt;strong&gt;Explore the example&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The bundled synthetic patch changes four files and produces five prompts, covering workflow privileges, destructive SQL, removed tests, workflow behavior and dependency reproducibility.&lt;/p&gt;

&lt;p&gt;You can also watch the &lt;a href="https://brunnojob.github.io/patchscope/docs/launch/demo.html" rel="noopener noreferrer"&gt;18-second illustrated walkthrough&lt;/a&gt;. It uses actual fixture output; the CI section illustrates the integration rather than recording the GitHub interface.&lt;/p&gt;

&lt;h2&gt;
  
  
  Add it to a pull request workflow
&lt;/h2&gt;

&lt;p&gt;Save this as &lt;code&gt;.github/workflows/patchscope.yml&lt;/code&gt;:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;/code&gt;`yaml&lt;br&gt;
name: PatchScope PR review&lt;/p&gt;

&lt;p&gt;on:&lt;br&gt;
  pull_request:&lt;/p&gt;

&lt;p&gt;permissions:&lt;br&gt;
  contents: read&lt;/p&gt;

&lt;p&gt;jobs:&lt;br&gt;
  review:&lt;br&gt;
    runs-on: ubuntu-latest&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;steps:
  - uses: actions/checkout@v4
    with:
      fetch-depth: 0
      persist-credentials: false

  - name: Create pull request diff
    shell: bash
    env:
      BASE_SHA: ${{ github.event.pull_request.base.sha }}
      HEAD_SHA: ${{ github.event.pull_request.head.sha }}
    run: |
      git diff --no-ext-diff --no-color \
        "$BASE_SHA...$HEAD_SHA" \
        &amp;gt; "$RUNNER_TEMP/patchscope.diff"

  - name: Build review checklist
    id: review
    uses: brunnojob/patchscope@v2.0.1
    with:
      diff-file: ${{ runner.temp }}/patchscope.diff

  - name: Keep review reports
    uses: actions/upload-artifact@v4
    with:
      name: patchscope-review
      retention-days: 7
      path: |
        ${{ steps.review.outputs.report-markdown }}
        ${{ steps.review.outputs.report-json }}
        ${{ steps.review.outputs.report-sarif }}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;`&lt;code&gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The workflow compares the PR head against its merge base with the target branch.&lt;/p&gt;

&lt;p&gt;It uses read-only repository permissions and does not install project dependencies or execute PR source code. For production, pin this and other third-party Actions to reviewed full commit SHAs.&lt;/p&gt;

&lt;p&gt;After the run, read the checklist in the job summary or download the report artifacts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Findings are advisory:&lt;/strong&gt; they do not fail the Action. A green job means analysis completed, not that the patch is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prefer the terminal?
&lt;/h2&gt;

&lt;p&gt;With Node.js 22+ and Git:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;/code&gt;`bash&lt;br&gt;
git clone &lt;a href="https://github.com/brunnojob/patchscope.git" rel="noopener noreferrer"&gt;https://github.com/brunnojob/patchscope.git&lt;/a&gt;&lt;br&gt;
cd patchscope&lt;/p&gt;

&lt;h1&gt;
  
  
  Analyze the bundled example
&lt;/h1&gt;

&lt;p&gt;node scripts/cli.mjs docs/example.diff --format markdown&lt;/p&gt;

&lt;h1&gt;
  
  
  Export structured results
&lt;/h1&gt;

&lt;p&gt;node scripts/cli.mjs docs/example.diff --format json&lt;br&gt;
node scripts/cli.mjs docs/example.diff --format sarif&lt;br&gt;
`&lt;code&gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;To inspect changes in another repository:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;/code&gt;`bash&lt;br&gt;
git diff --no-ext-diff --no-color HEAD &amp;gt; change.diff&lt;/p&gt;

&lt;p&gt;node /path/to/patchscope/scripts/cli.mjs \&lt;br&gt;
  change.diff --format markdown&lt;br&gt;
`&lt;code&gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The CLI also supports explicit severity thresholds, configurable rule priorities and suppressions with documented reasons.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it helps—and its limits
&lt;/h2&gt;

&lt;p&gt;PatchScope is useful when you want an inspectable starting point for reviewing a change.&lt;/p&gt;

&lt;p&gt;It does not understand an entire application, measure test coverage, execute tests or replace secret scanning. Its dependency and test prompts describe the patch, including the context missing from unchanged files.&lt;/p&gt;

&lt;p&gt;Reports omit raw patch lines and detected credential values. Filenames and configured suppression reasons can still be sensitive, so review exports before sharing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it on a real review
&lt;/h2&gt;

&lt;p&gt;PatchScope is free and MIT licensed.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/marketplace/actions/patchscope-diff-review" rel="noopener noreferrer"&gt;Install the GitHub Action&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://brunnojob.github.io/patchscope/" rel="noopener noreferrer"&gt;Try the browser workbench&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/brunnojob/patchscope#readme" rel="noopener noreferrer"&gt;Read the documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/brunnojob/patchscope/issues" rel="noopener noreferrer"&gt;Report a sanitized edge case&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What recurring change would you want a review checklist to highlight—and what would make that prompt useful rather than noisy?&lt;/p&gt;




&lt;p&gt;If PatchScope helps your workflow, you can optionally &lt;a href="https://donate.stripe.com/6oU8wQg9k9Hb8809CrfQI01" rel="noopener noreferrer"&gt;support its maintenance through Stripe&lt;/a&gt;. All features remain free.`&lt;/p&gt;

</description>
      <category>githubactions</category>
      <category>opensource</category>
      <category>devops</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Offshore Fleet Safety</title>
      <dc:creator>brunnodev</dc:creator>
      <pubDate>Wed, 21 Oct 2026 06:40:47 +0000</pubDate>
      <link>https://dev.to/brunnojob/offshore-fleet-safety-3g4b</link>
      <guid>https://dev.to/brunnojob/offshore-fleet-safety-3g4b</guid>
      <description>&lt;p&gt;Crew registration, activation and vessel assignment.&lt;/p&gt;

&lt;p&gt;Station rules with staffing minimums and required certificates.&lt;/p&gt;

&lt;p&gt;Certificate expiry checks against Unix timestamps.&lt;/p&gt;

&lt;p&gt;Vessel isolation and prevention of simultaneous station assignments.&lt;/p&gt;

&lt;p&gt;Idempotent attendance, station occupancy and staffing shortages.&lt;/p&gt;

&lt;p&gt;Monotonic drill duration and prevention of completed drill ID reuse.&lt;/p&gt;

&lt;p&gt;Ordered audit events with an extensible repository interface.&lt;/p&gt;

&lt;p&gt;Mutex-protected operations and an independently synchronized memory repository.&lt;/p&gt;

&lt;p&gt;Input validation, structured status reporting and native regression tests.&lt;/p&gt;

&lt;p&gt;(&lt;a href="https://github.com/brunnojob/ofs2x-offshore-operations/raw/refs/heads/main/evidence/demo.mp4" rel="noopener noreferrer"&gt;https://github.com/brunnojob/ofs2x-offshore-operations/raw/refs/heads/main/evidence/demo.mp4&lt;/a&gt;)&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>backend</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>I built a free interactive simulation lab to help beginners learn logic and Git/GitHub directly in the browser (No tokens required)</title>
      <dc:creator>brunnodev</dc:creator>
      <pubDate>Tue, 20 Oct 2026 20:51:46 +0000</pubDate>
      <link>https://dev.to/brunnojob/i-built-a-free-interactive-simulation-lab-to-help-beginners-learn-logic-and-gitgithub-directly-in-35nj</link>
      <guid>https://dev.to/brunnojob/i-built-a-free-interactive-simulation-lab-to-help-beginners-learn-logic-and-gitgithub-directly-in-35nj</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdejbhbx9kadozadlphro.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdejbhbx9kadozadlphro.jpg" alt=" " width="800" height="390"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hey everyone,&lt;/p&gt;

&lt;p&gt;I created DevStart Lab, an open-source, browser-based sandbox to help beginners practice programming logic and GitHub workflows (like issues, branches, and PRs) in a completely safe environment. No installation, backend setup, or API tokens are required.&lt;/p&gt;

&lt;p&gt;It is fully localized in English and Portuguese. I built this purely to give back to the community and help those struggling with their first open-source contributions. Hope it helps someone out there!&lt;/p&gt;

&lt;p&gt;Live Project: &lt;a href="https://brunnojob.github.io/devstart-lab/" rel="noopener noreferrer"&gt;https://brunnojob.github.io/devstart-lab/&lt;/a&gt;&lt;br&gt;
Source Code: &lt;a href="https://github.com/brunnojob/devstart-lab" rel="noopener noreferrer"&gt;https://github.com/brunnojob/devstart-lab&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  opensource, #github, #beginners, #webdev
&lt;/h1&gt;

</description>
      <category>beginners</category>
      <category>githubactions</category>
      <category>github</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
