aist-security-check

Audit changed files for security risks and produce remediation findings.

Updated Aug 31, 2025
One-click install
npx skills add https://github.com/aist-ai-sast/aist --skill aist-security-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aist-security-check
Source: https://github.com/aist-ai-sast/aist/tree/main/.claude/skills/aist-security-check
Command: npx skills add https://github.com/aist-ai-sast/aist --skill aist-security-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables deep security audits of changed files to detect org boundary violations, path traversal risks, missing authentication, raw SQL injection, and hardcoded credentials.

Core Features & Use Cases

  • Comprehensive security review of code changes across repositories.
  • Detects common vulnerabilities such as broken access controls, path traversal, SQL injection, and credential exposure, with actionable remediation guidance.
  • Supports integration into CI/CD workflows and developer review processes to accelerate secure releases.

Quick Start

Run the security audit on changed files and review the findings to remediate vulnerabilities.

Frequently Asked Questions about aist-security-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan changed files for hardcoded credentials and SQL injection in a pull request?

You can audit code changes for hardcoded credentials and SQL injection by running a deep security review. This process detects vulnerabilities in changed files across repositories and produces structured findings suitable for developer remediation.

What is an org boundary violation in code and how does a security audit detect it?

An org boundary violation involves unauthorized data access across organizational limits. A security audit detects this by reviewing changed files in pull requests, identifying broken access controls alongside path traversal risks to ensure secure boundaries.

Can I integrate automated vulnerability detection into my CI pipeline?

Yes, automated vulnerability detection integrates into CI pipelines. The security audit supports CI/CD workflows and code review processes, scanning changed content to detect missing authentication and path traversal risks to accelerate secure releases.

How do I find missing authentication and path traversal risks during code review?

To find missing authentication and path traversal risks during code review, run a security audit on changed files. It identifies these vulnerabilities across repositories and generates structured findings to guide developer remediation.

Does this security audit work with existing CI tooling and pull request workflows?

Yes, the security audit works with existing CI tooling and pull request workflows. It integrates into CI pipelines and developer review processes, scanning changed content to produce structured findings suitable for developer remediation.