Skills reviewdog
๐Ÿ“ฆ

reviewdog

v0.1.0 Content revision r2 Critical ๐Ÿ“ Filesystem access๐Ÿ”‘ Env variables๐ŸŒ Network accessโšก Contains scriptsโš™๏ธ External commands

Integrate Reviewdog Security Feedback into CI

Security scanner results are often fragmented across CI logs. This skill helps configure reviewdog to publish focused findings in pull requests and local hooks.

Supports: Claude Codex Code(CC)
โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "reviewdog" from https://skillstore.io/skills/agentsecops-reviewdog.md and its manifest at https://skillstore.io/api/skills/agentsecops-reviewdog/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "reviewdog". Configure Bandit for local Python review.

Expected outcome:

  • A local reporter configuration for Bandit findings.
  • A changed-line filter and blocking error threshold.
  • Required reviewdog and Bandit installation steps.

Using "reviewdog". Add Semgrep and Gitleaks to GitHub pull requests.

Expected outcome:

  • A pull request workflow with minimal write permissions.
  • Separate critical and warning review channels.
  • Pinned dependencies and fail-closed scanner handling.

Using "reviewdog". Integrate a custom scanner with reviewdog.

Expected outcome:

A format selection, field mapping, reporter choice, severity policy, and validation checklist for the custom scanner.

Security Audit

Critical
v9 โ€ข 7/23/2026 Open versioned report

Most static alerts are false positives caused by Markdown code spans, documentation URLs, /dev/null redirection, and references to platform-managed CI tokens. The GitLab template critically downloads a mutable remote installer and pipes it directly to sh. The templates also use predictable temporary files, unpinned CI dependencies, and fail-open secret-scanning patterns.

9
Files scanned
2,206
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (3)

Critical
Pipe to shell pattern
curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b /usr
The CI template downloads an installer from the mutable master branch and immediately executes it with sh. A compromised upstream response would gain code execution in the runner.
High
Mutable CI Dependencies Execute in a Privileged Workflow
The GitHub workflow uses a mutable major action tag, requests the latest reviewdog release, and installs unpinned Python packages. Upstream changes can execute before later steps receive a write-capable GitHub token.
The mutable action tag, latest version selector, and unpinned package installation are explicit. The workflow also grants pull-request and checks write permissions.
High
Critical Secret Scans Fail Open
Gitleaks failures are suppressed with true, and missing reports can produce empty findings or skip reviewdog. Scanner crashes can therefore pass the critical secret gate.
Each configuration explicitly suppresses the Gitleaks exit status. At least one path substitutes empty findings or skips review processing when output is absent.
Capability review items (4)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Hardcoded URL
curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b /usr
This URL targets a mutable master-branch installer that is fetched during CI and passed directly to sh. The network dependency is not pinned or integrity-verified.
Medium
Temp directory access
gitleaks detect --report-format json --report-path /tmp/gitleaks.json --no-git 2>/dev/null || true
Gitleaks writes sensitive scan output to the predictable shared path /tmp/gitleaks.json. On a shared host, collisions or symlink attacks could overwrite another file or expose findings.
Medium
Temp directory access
cat /tmp/gitleaks.json 2>/dev/null || echo '{"findings":[]}'
The runner reads scan results from the predictable shared path /tmp/gitleaks.json. A colliding or attacker-controlled file could be accepted as trusted scanner output.
Medium
Temp directory access
entry: bash -c 'gitleaks detect --report-format json --report-path /tmp/gitleaks.json --no-git 2>/de
The pre-commit hook writes and reads Gitleaks results at the fixed shared path /tmp/gitleaks.json. This permits collisions and symlink manipulation on multi-user systems.

Risk Factors

๐Ÿ“ Filesystem access (34)
๐Ÿ”‘ Env variables (17)
๐ŸŒ Network access (19)
โšก Contains scripts (2)
โš™๏ธ External commands (49)

Detected Patterns

Pipe to shell pattern
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/agentsecops-reviewdog/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/agentsecops-reviewdog/security.svg)](https://skillstore.io/skills/agentsecops-reviewdog?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/agentsecops-reviewdog?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentsecops-reviewdog/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/agentsecops-reviewdog.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

AgentSecOps. (2026). reviewdog security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/agentsecops-reviewdog/audits/9

BibTeX citation

@techreport{agentsecops-agentsecops-reviewdog-2026, author = {AgentSecOps}, title = {reviewdog security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/agentsecops-reviewdog/audits/9}, note = {Author version 0.1.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "reviewdog security audit report (audit version 9)" version: "0.1.0" type: report authors: - name: "AgentSecOps" date-released: "2026-07-23" url: "https://skillstore.io/skills/agentsecops-reviewdog/audits/9" identifiers: - type: other value: "skillstore:agentsecops-reviewdog:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
59
Architecture
100
Maintainability
87
Content
71
Community
91
Spec Compliance

What You Can Build

Add Pull Request Security Comments

Publish Bandit and Semgrep findings on changed lines in GitHub pull requests.

Standardize GitLab Security Gates

Combine multiple scanners into consistent merge request discussions and blocking thresholds.

Run Local Pre-Commit Reviews

Surface security and lint findings before code reaches the remote repository.

Try These Prompts

Create a Basic Local Setup
Configure reviewdog for [language] using [scanner]. Use the local reporter, scan changed files, and explain required dependencies.
Add a GitHub Actions Review
Create a GitHub Actions reviewdog workflow for [scanners]. Use least-privilege permissions, pinned dependencies, and pull request annotations.
Build a GitLab Security Gate
Design a GitLab CI reviewdog pipeline for [scanners]. Block [severity] findings and report lower severities without suppressing scanner failures.
Design a Multi-Tool Policy
Create a reviewdog policy for [repository]. Define reporters, diff filters, severity mappings, failure behavior, token permissions, and verified dependency versions.

Best Practices

  • Pin actions, packages, installers, and container images to reviewed immutable versions.
  • Grant reporter tokens only the repository permissions required for comments and checks.
  • Fail closed when a critical scanner crashes or produces an invalid report.

Avoid

  • Do not pipe remote installation scripts directly into a shell.
  • Do not suppress every scanner error with unconditional success handling.
  • Do not expose broad write tokens to unpinned tools or untrusted pull request workflows.

Frequently Asked Questions

Does this skill run security scanners itself?
No. It provides guidance and templates for connecting installed scanners to reviewdog.
Which code hosting platforms are covered?
The included guidance covers GitHub and GitLab, with reference material for Bitbucket and Gerrit reporters.
Can reviewdog block a pull request?
Yes. Configure failure thresholds and required CI checks so selected finding levels block merging.
Which scanners are included in the templates?
Examples cover Bandit, Semgrep, Gitleaks, Hadolint, Checkov, and ShellCheck.
Does reviewdog remove scanner false positives?
No. It filters and reports findings, while scanner rules and suppressions control false positives.
How should CI tokens be configured?
Store tokens in platform secrets, grant minimal permissions, and avoid exposing them to untrusted or mutable dependencies.

Developer Details

License

MIT

Author version

v0.1.0

Skillstore revision

r2

Ref

9e952417e76879bc9d853e1b8b2cd6d6d8d4a1c2

Maintenance freshness

7/24/2026

Usage

9 downloads ยท 261 views

File structure

๐Ÿ“ assets/

๐Ÿ“„ .gitkeep

๐Ÿ“„ .reviewdog.yml

๐Ÿ“„ github_actions_template.yml

๐Ÿ“„ gitlab_ci_template.yml

๐Ÿ“„ pre_commit_config.yaml

๐Ÿ“ references/

๐Ÿ“„ cwe_mapping.md

๐Ÿ“„ reporter_formats.md

๐Ÿ“„ supported_tools.md

๐Ÿ“„ SKILL.md