[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B91HN37G79YC89C9TDF3D":3,"skill-same:01M71B91HN37G79YC89C9TDF3D":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":78},"01M71B91HN37G79YC89C9TDF3D","cyber-integrating-sast-into-github-actions-pipeline",null,"This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI\u002FCD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and establishing quality gates that block merges when high-severity vulnerabilities are detect","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-integrating-sast-into-github-actions-pipeline\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"actions","github actions","cyber integrating sast into github actions pipeline","sast","github","integrating sast into github actions pipeline","pipeline","semgrep","scanning","pull requests","code","reduce","when","codeql","false","cybersecurity","ci","testing","static","advanced","2026-11-10 10:12:30",false,"---\nname: cyber-integrating-sast-into-github-actions-pipeline\ndescription: \"This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI\u002FCD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and establishing quality gates that block merges when high-severity vulnerabilities are detect\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: integrating-sast-into-github-actions-pipeline | description: 'This skill covers integrating Static Application Security Testing (SAST) |   tools—CodeQL and Semgrep—into GitHub Actions CI\u002FCD pipelines. It addresses configuring |   automated code scanning on pull requests and pushes, tuning rules to reduce false |   positives, uploading SARIF results to GitHub Advanced Security, and establishing |   quality gates that block merges when high-severity vulnerabilities are detected. |  |   ' | d\"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Integrating SAST into GitHub Actions Pipeline\n\n## When to Use\n\n- When development teams need automated code-level vulnerability detection on every pull request\n- When security teams require consistent SAST enforcement across all repositories in an organization\n- When migrating from manual or periodic security reviews to continuous security testing\n- When compliance frameworks (SOC 2, PCI DSS, NIST SSDF) require evidence of automated code analysis\n- When multiple languages coexist in a monorepo and need unified scanning under one workflow\n\n**Do not use** for runtime vulnerability detection (use DAST instead), for scanning third-party dependencies (use SCA tools like Snyk), or for infrastructure-as-code scanning (use Checkov or tfsec).\n\n## Prerequisites\n\n- GitHub repository with GitHub Actions enabled\n- GitHub Advanced Security license (required for CodeQL on private repos; free for public repos)\n- Semgrep account for managed rules and Semgrep App dashboard (free tier available)\n- Repository code in a supported language: Python, JavaScript\u002FTypeScript, Java, C\u002FC++, C#, Go, Ruby, Swift, Kotlin\n\n## Workflow\n\n### Step 1: Configure CodeQL Analysis Workflow\n\nCreate a CodeQL workflow that runs on pull requests and on a weekly schedule to catch vulnerabilities in existing code.\n\n```yaml\n# .github\u002Fworkflows\u002Fcodeql-analysis.yml\nname: \"CodeQL Analysis\"\n\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n    branches: [main]\n  schedule:\n    - cron: '30 2 * * 1'  # Weekly Monday 2:30 AM\n\njobs:\n  analyze:\n    name: Analyze (${{ matrix.language }})\n    runs-on: ubuntu-latest\n    permissions:\n      actions: read\n      contents: read\n      security-events: write\n\n    strategy:\n      fail-fast: false\n      matrix:\n        language: ['javascript', 'python']\n\n    steps:\n      - name: Checkout repository\n        uses: actions\u002Fcheckout@v4\n\n      - name: Initialize CodeQL\n        uses: github\u002Fcodeql-action\u002Finit@v3\n        with:\n          languages: ${{ matrix.language }}\n          queries: security-extended,security-and-quality\n\n      - name: Autobuild\n        uses: github\u002Fcodeql-action\u002Fautobuild@v3\n\n      - name: Perform CodeQL Analysis\n        uses: github\u002Fcodeql-action\u002Fanalyze@v3\n        with:\n          category: \"\u002Flanguage:${{ matrix.language }}\"\n```\n\n### Step 2: Add Semgrep Scanning for Custom Rules\n\nSemgrep complements CodeQL with faster scans and support for custom pattern-based rules. Configure it to upload SARIF results to the same GitHub Security tab.\n\n```yaml\n# .github\u002Fworkflows\u002Fsemgrep.yml\nname: \"Semgrep SAST Scan\"\n\non:\n  pull_request:\n    branches: [main, develop]\n  push:\n    branches: [main]\n\njobs:\n  semgrep:\n    name: Semgrep Scan\n    runs-on: ubuntu-latest\n    permissions:\n      security-events: write\n      contents: read\n\n    container:\n      image: semgrep\u002Fsemgrep:latest\n\n    steps:\n      - name: Checkout\n        uses: actions\u002Fcheckout@v4\n\n      - name: Run Semgrep\n        run: |\n          semgrep ci \\\n            --config auto \\\n            --config p\u002Fowasp-top-ten \\\n            --config p\u002Fcwe-top-25 \\\n            --sarif --output semgrep-results.sarif \\\n            --severity ERROR \\\n            --error\n        env:\n          SEMGREP_APP_TOKEN: ${{ secrets.SEMGREP_APP_TOKEN }}\n\n      - name: Upload SARIF\n        if: always()\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        with:\n          sarif_file: semgrep-results.sarif\n          category: semgrep\n```\n\n### Step 3: Create Custom Semgrep Rules for Organization Patterns\n\nWrite organization-specific rules to catch patterns unique to your codebase, such as deprecated internal APIs or insecure configuration patterns.\n\n```yaml\n# .semgrep\u002Fcustom-rules.yml\nrules:\n  - id: hardcoded-database-url\n    patterns:\n      - pattern: |\n          $DB_URL = \"...$PROTO:\u002F\u002F...:...$PASS@...\"\n    message: |\n      Hardcoded database connection string with credentials detected.\n      Use environment variables or a secrets manager instead.\n    languages: [python, javascript, typescript]\n    severity: ERROR\n    metadata:\n      cwe: \"CWE-798: Use of Hard-coded Credentials\"\n      owasp: \"A07:2021 - Identification and Authentication Failures\"\n\n  - id: unsafe-deserialization\n    patterns:\n      - pattern-either:\n          - pattern: pickle.loads(...)\n          - pattern: yaml.load(..., Loader=yaml.Loader)\n          - pattern: yaml.load(..., Loader=yaml.FullLoader)\n    message: |\n      Unsafe deserialization detected. Use safe alternatives to prevent\n      remote code execution vulnerabilities.\n    languages: [python]\n    severity: ERROR\n    metadata:\n      cwe: \"CWE-502: Deserialization of Untrusted Data\"\n\n  - id: missing-csrf-protection\n    patterns:\n      - pattern: |\n          @app.route(\"...\", methods=[\"POST\"])\n          def $FUNC(...):\n              ...\n      - pattern-not-inside: |\n          @csrf.exempt\n          ...\n    message: \"POST endpoint may lack CSRF protection.\"\n    languages: [python]\n    severity: WARNING\n```\n\n### Step 4: Establish Quality Gates with Branch Protection\n\nConfigure branch protection rules that require SAST checks to pass before merging, preventing vulnerable code from reaching production branches.\n\n```bash\n# Use GitHub CLI to set branch protection requiring SAST checks\ngh api repos\u002F{owner}\u002F{repo}\u002Fbranches\u002Fmain\u002Fprotection \\\n  --method PUT \\\n  --field required_status_checks='{\"strict\":true,\"contexts\":[\"Analyze (javascript)\",\"Analyze (python)\",\"Semgrep Scan\"]}' \\\n  --field enforce_admins=true \\\n  --field required_pull_request_reviews='{\"required_approving_review_count\":1}'\n```\n\n### Step 5: Tune and Suppress False Positives\n\nManage false positives through CodeQL query filters and Semgrep nosemgrep annotations to maintain developer trust in scan results.\n\n```yaml\n# codeql-config.yml - Custom CodeQL configuration\nname: \"Custom CodeQL Config\"\nqueries:\n  - uses: security-extended\n  - uses: security-and-quality\n  - excludes:\n      id: js\u002Funused-local-variable\npaths-ignore:\n  - '**\u002Ftest\u002F**'\n  - '**\u002Ftests\u002F**'\n  - '**\u002Fvendor\u002F**'\n  - '**\u002Fnode_modules\u002F**'\n  - '**\u002F*.test.js'\n  - '**\u002F*.spec.py'\n```\n\n```python\n# Example: Suppressing a known false positive in Semgrep\nimport subprocess\n\ndef run_safe_command(cmd_list):\n    # nosemgrep: python.lang.security.audit.dangerous-subprocess-use\n    result = subprocess.run(cmd_list, capture_output=True, text=True, shell=False)\n    return result.stdout\n```\n\n### Step 6: Aggregate and Report Findings\n\nUse the GitHub Security Overview dashboard and configure notifications for security alerts across repositories.\n\n```bash\n# Query SARIF results via GitHub API for reporting\ngh api repos\u002F{owner}\u002F{repo}\u002Fcode-scanning\u002Falerts \\\n  --jq '.[] | select(.state==\"open\") | {rule: .rule.id, severity: .rule.security_severity_level, file: .most_recent_instance.location.path, line: .most_recent_instance.location.start_line}'\n\n# Count open alerts by severity\ngh api repos\u002F{owner}\u002F{repo}\u002Fcode-scanning\u002Falerts \\\n  --jq '[.[] | select(.state==\"open\")] | group_by(.rule.security_severity_level) | map({severity: .[0].rule.security_severity_level, count: length})'\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| SAST | Static Application Security Testing — analyzes source code without executing it to find security vulnerabilities |\n| SARIF | Static Analysis Results Interchange Format — standardized JSON format for expressing results from static analysis tools |\n| CodeQL | GitHub's semantic code analysis engine that treats code as data and queries it for vulnerability patterns |\n| Semgrep | Lightweight static analysis tool using pattern matching to find bugs and security issues across many languages |\n| Security Extended | CodeQL query suite that includes additional security queries beyond the default set for deeper analysis |\n| Quality Gate | Automated checkpoint that blocks code from progressing through the pipeline unless security criteria are met |\n| False Positive | A scan finding that incorrectly identifies secure code as vulnerable, requiring suppression or tuning |\n\n## Tools & Systems\n\n- **CodeQL**: GitHub's semantic code analysis engine with deep dataflow and taint tracking analysis\n- **Semgrep**: Fast, lightweight pattern-matching SAST tool with 3000+ community rules and custom rule support\n- **GitHub Advanced Security**: Platform providing code scanning, secret scanning, and dependency review in GitHub\n- **SARIF Viewer**: VS Code extension for reviewing SARIF results locally during development\n- **GitHub Security Overview**: Organization-level dashboard aggregating security alerts across all repositories\n\n## Common Scenarios\n\n### Scenario: Monorepo with Multiple Languages Needs Unified SAST\n\n**Context**: A platform team manages a monorepo containing Python microservices, TypeScript frontends, and Go infrastructure tools. Security reviews happen manually every quarter, missing vulnerabilities between reviews.\n\n**Approach**:\n1. Configure CodeQL with a matrix strategy covering Python, JavaScript, and Go languages\n2. Add Semgrep with `--config auto` to detect language automatically and apply relevant rulesets\n3. Create path-based triggers so only changed language directories trigger their respective scans\n4. Upload all SARIF results to GitHub Security tab with unique categories per tool and language\n5. Set branch protection requiring all SAST jobs to pass before merge\n6. Schedule weekly full-repository scans to catch issues in unchanged code from newly published CVE patterns\n\n**Pitfalls**: Setting CodeQL to analyze all languages on every PR increases CI time significantly. Use path filters to trigger only relevant language scans. Semgrep's `--config auto` may enable rules that conflict with CodeQL findings, creating duplicate alerts.\n\n### Scenario: Reducing Alert Fatigue from High False Positive Rate\n\n**Context**: After enabling SAST, developers ignore findings because 40% are false positives, undermining the security program.\n\n**Approach**:\n1. Export all current alerts and categorize them as true positive, false positive, or informational\n2. Create a custom CodeQL config excluding noisy query IDs that produce the most false positives\n3. Write `.semgrepignore` patterns for test files, generated code, and vendored dependencies\n4. Establish a weekly triage meeting where security and development leads review new rule additions\n5. Track false positive rate as a metric and target below 15% for developer trust\n\n**Pitfalls**: Over-suppressing rules to reduce noise can create blind spots. Always validate suppressions against the OWASP Top 10 and CWE Top 25 to ensure critical vulnerability classes remain covered.\n\n## Output Format\n\n```\nSAST Pipeline Scan Report\n==========================\nRepository: org\u002Fweb-application\nBranch: feature\u002Fuser-auth-refactor\nScan Date: 2026-02-23\nCommit: a1b2c3d4\n\nCodeQL Results:\n  Language    Queries Run   Findings   Critical   High   Medium\n  javascript  312           4          1          2      1\n  python      287           2          0          1      1\n\nSemgrep Results:\n  Ruleset          Rules Matched   Findings   Errors   Warnings\n  auto             1,847           3          1        2\n  owasp-top-ten    186             2          1        1\n  custom-rules     12              1          0        1\n\nQUALITY GATE: FAILED\n  Blocking findings: 2 Critical\u002FHigh severity issues\n  - [CRITICAL] CWE-89: SQL Injection in src\u002Fapi\u002Fusers.py:47\n  - [HIGH] CWE-79: Cross-site Scripting in src\u002Fcomponents\u002FSearch.tsx:123\n\nAction Required: Fix blocking findings before merge is permitted.\n```\n","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Integrating SAST into GitHub Actions Pipeline\n\n## When to Use\n\n- When development teams need automated code-level vulnerability detection on every pull request\n- When security teams require consistent SAST enforcement across all repositories in an organization\n- When migrating from manual or periodic security reviews to continuous security testing\n- When compliance frameworks (SOC 2, PCI DSS, NIST SSDF) require evidence of automated code analysis\n- When multiple languages coexist in a monorepo and need unified scanning under one workflow\n\n**Do not use** for runtime vulnerability detection (use DAST instead), for scanning third-party dependencies (use SCA tools like Snyk), or for infrastructure-as-code scanning (use Checkov or tfsec).\n\n## Prerequisites\n\n- GitHub repository with GitHub Actions enabled\n- GitHub Advanced Security license (required for CodeQL on private repos; free for public repos)\n- Semgrep account for managed rules and Semgrep App dashboard (free tier available)\n- Repository code in a supported language: Python, JavaScript\u002FTypeScript, Java, C\u002FC++, C#, Go, Ruby, Swift, Kotlin\n\n## Workflow\n\n### Step 1: Configure CodeQL Analysis Workflow\n\nCreate a CodeQL workflow that runs on pull requests and on a weekly schedule to catch vulnerabilities in existing code.\n\n```yaml\n# .github\u002Fworkflows\u002Fcodeql-analysis.yml\nname: \"CodeQL Analysis\"\n\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n    branches: [main]\n  schedule:\n    - cron: '30 2 * * 1'  # Weekly Monday 2:30 AM\n\njobs:\n  analyze:\n    name: Analyze (${{ matrix.language }})\n    runs-on: ubuntu-latest\n    permissions:\n      actions: read\n      contents: read\n      security-events: write\n\n    strategy:\n      fail-fast: false\n      matrix:\n        language: ['javascript', 'python']\n\n    steps:\n      - name: Checkout repository\n        uses: actions\u002Fcheckout@v4\n\n      - name: Initialize CodeQL\n        uses: github\u002Fcodeql-action\u002Finit@v3\n        with:\n          languages: ${{ matrix.language }}\n          queries: security-extended,security-and-quality\n\n      - name: Autobuild\n        uses: github\u002Fcodeql-action\u002Fautobuild@v3\n\n      - name: Perform CodeQL Analysis\n        uses: github\u002Fcodeql-action\u002Fanalyze@v3\n        with:\n          category: \"\u002Flanguage:${{ matrix.language }}\"\n```\n\n### Step 2: Add Semgrep Scanning for Custom Rules\n\nSemgrep complements CodeQL with faster scans and support for custom pattern-based rules. Configure it to upload SARIF results to the same GitHub Security tab.\n\n```yaml\n# .github\u002Fworkflows\u002Fsemgrep.yml\nname: \"Semgrep SAST Scan\"\n\non:\n  pull_request:\n    branches: [main, develop]\n  push:\n    branches: [main]\n\njobs:\n  semgrep:\n    name: Semgrep Scan\n    runs-on: ubuntu-latest\n    permissions:\n      security-events: write\n      contents: read\n\n    container:\n      image: semgrep\u002Fsemgrep:latest\n\n    steps:\n      - name: Checkout\n        uses: actions\u002Fcheckout@v4\n\n      - name: Run Semgrep\n        run: |\n          semgrep ci \\\n            --config auto \\\n            --config p\u002Fowasp-top-ten \\\n            --config p\u002Fcwe-top-25 \\\n            --sarif --output semgrep-results.sarif \\\n            --severity ERROR \\\n            --error\n        env:\n          SEMGREP_APP_TOKEN: ${{ secrets.SEMGREP_APP_TOKEN }}\n\n      - name: Upload SARIF\n        if: always()\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        with:\n          sarif_file: semgrep-results.sarif\n          category: semgrep\n```\n\n### Step 3: Create Custom Semgrep Rules for Organization Patterns\n\nWrite organization-specific rules to catch patterns unique to your codebase, such as deprecated internal APIs or insecure configuration patterns.\n\n```yaml\n# .semgrep\u002Fcustom-rules.yml\nrules:\n  - id: hardcoded-database-url\n    patterns:\n      - pattern: |\n          $DB_URL = \"...$PROTO:\u002F\u002F...:...$PASS@...\"\n    message: |\n      Hardcoded database connection string with credentials detected.\n      Use environment variables or a secrets manager instead.\n    languages: [python, javascript, typescript]\n    severity: ERROR\n    metadata:\n      cwe: \"CWE-798: Use of Hard-coded Credentials\"\n      owasp: \"A07:2021 - Identification and Authentication Failures\"\n\n  - id: unsafe-deserialization\n    patterns:\n      - pattern-either:\n          - pattern: pickle.loads(...)\n          - pattern: yaml.load(..., Loader=yaml.Loader)\n          - pattern: yaml.load(..., Loader=yaml.FullLoader)\n    message: |\n      Unsafe deserialization detected. Use safe alternatives to prevent\n      remote code execution vulnerabilities.\n    languages: [python]\n    severity: ERROR\n    metadata:\n      cwe: \"CWE-502: Deserialization of Untrusted Data\"\n\n  - id: missing-csrf-protection\n    patterns:\n      - pattern: |\n          @app.route(\"...\", methods=[\"POST\"])\n          def $FUNC(...):\n              ...\n      - pattern-not-inside: |\n          @csrf.exempt\n          ...\n    message: \"POST endpoint may lack CSRF protection.\"\n    languages: [python]\n    severity: WARNING\n```\n\n### Step 4: Establish Quality Gates with Branch Protection\n\nConfigure branch protection rules that require SAST checks to pass before merging, preventing vulnerable code from reaching production branches.\n\n```bash\n# Use GitHub CLI to set branch protection requiring SAST checks\ngh api repos\u002F{owner}\u002F{repo}\u002Fbranches\u002Fmain\u002Fprotection \\\n  --method PUT \\\n  --field required_status_checks='{\"strict\":true,\"contexts\":[\"Analyze (javascript)\",\"Analyze (python)\",\"Semgrep Scan\"]}' \\\n  --field enforce_admins=true \\\n  --field required_pull_request_reviews='{\"required_approving_review_count\":1}'\n```\n\n### Step 5: Tune and Suppress False Positives\n\nManage false positives through CodeQL query filters and Semgrep nosemgrep annotations to maintain developer trust in scan results.\n\n```yaml\n# codeql-config.yml - Custom CodeQL configuration\nname: \"Custom CodeQL Config\"\nqueries:\n  - uses: security-extended\n  - uses: security-and-quality\n  - excludes:\n      id: js\u002Funused-local-variable\npaths-ignore:\n  - '**\u002Ftest\u002F**'\n  - '**\u002Ftests\u002F**'\n  - '**\u002Fvendor\u002F**'\n  - '**\u002Fnode_modules\u002F**'\n  - '**\u002F*.test.js'\n  - '**\u002F*.spec.py'\n```\n\n```python\n# Example: Suppressing a known false positive in Semgrep\nimport subprocess\n\ndef run_safe_command(cmd_list):\n    # nosemgrep: python.lang.security.audit.dangerous-subprocess-use\n    result = subprocess.run(cmd_list, capture_output=True, text=True, shell=False)\n    return result.stdout\n```\n\n### Step 6: Aggregate and Report Findings\n\nUse the GitHub Security Overview dashboard and configure notifications for security alerts across repositories.\n\n```bash\n# Query SARIF results via GitHub API for reporting\ngh api repos\u002F{owner}\u002F{repo}\u002Fcode-scanning\u002Falerts \\\n  --jq '.[] | select(.state==\"open\") | {rule: .rule.id, severity: .rule.security_severity_level, file: .most_recent_instance.location.path, line: .most_recent_instance.location.start_line}'\n\n# Count open alerts by severity\ngh api repos\u002F{owner}\u002F{repo}\u002Fcode-scanning\u002Falerts \\\n  --jq '[.[] | select(.state==\"open\")] | group_by(.rule.security_severity_level) | map({severity: .[0].rule.security_severity_level, count: length})'\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| SAST | Static Application Security Testing — analyzes source code without executing it to find security vulnerabilities |\n| SARIF | Static Analysis Results Interchange Format — standardized JSON format for expressing results from static analysis tools |\n| CodeQL | GitHub's semantic code analysis engine that treats code as data and queries it for vulnerability patterns |\n| Semgrep | Lightweight static analysis tool using pattern matching to find bugs and security issues across many languages |\n| Security Extended | CodeQL query suite that includes additional security queries beyond the default set for deeper analysis |\n| Quality Gate | Automated checkpoint that blocks code from progressing through the pipeline unless security criteria are met |\n| False Positive | A scan finding that incorrectly identifies secure code as vulnerable, requiring suppression or tuning |\n\n## Tools & Systems\n\n- **CodeQL**: GitHub's semantic code analysis engine with deep dataflow and taint tracking analysis\n- **Semgrep**: Fast, lightweight pattern-matching SAST tool with 3000+ community rules and custom rule support\n- **GitHub Advanced Security**: Platform providing code scanning, secret scanning, and dependency review in GitHub\n- **SARIF Viewer**: VS Code extension for reviewing SARIF results locally during development\n- **GitHub Security Overview**: Organization-level dashboard aggregating security alerts across all repositories\n\n## Common Scenarios\n\n### Scenario: Monorepo with Multiple Languages Needs Unified SAST\n\n**Context**: A platform team manages a monorepo containing Python microservices, TypeScript frontends, and Go infrastructure tools. Security reviews happen manually every quarter, missing vulnerabilities between reviews.\n\n**Approach**:\n1. Configure CodeQL with a matrix strategy covering Python, JavaScript, and Go languages\n2. Add Semgrep with `--config auto` to detect language automatically and apply relevant rulesets\n3. Create path-based triggers so only changed language directories trigger their respective scans\n4. Upload all SARIF results to GitHub Security tab with unique categories per tool and language\n5. Set branch protection requiring all SAST jobs to pass before merge\n6. Schedule weekly full-repository scans to catch issues in unchanged code from newly published CVE patterns\n\n**Pitfalls**: Setting CodeQL to analyze all languages on every PR increases CI time significantly. Use path filters to trigger only relevant language scans. Semgrep's `--config auto` may enable rules that conflict with CodeQL findings, creating duplicate alerts.\n\n### Scenario: Reducing Alert Fatigue from High False Positive Rate\n\n**Context**: After enabling SAST, developers ignore findings because 40% are false positives, undermining the security program.\n\n**Approach**:\n1. Export all current alerts and categorize them as true positive, false positive, or informational\n2. Create a custom CodeQL config excluding noisy query IDs that produce the most false positives\n3. Write `.semgrepignore` patterns for test files, generated code, and vendored dependencies\n4. Establish a weekly triage meeting where security and development leads review new rule additions\n5. Track false positive rate as a metric and target below 15% for developer trust\n\n**Pitfalls**: Over-suppressing rules to reduce noise can create blind spots. Always validate suppressions against the OWASP Top 10 and CWE Top 25 to ensure critical vulnerability classes remain covered.\n\n## Output Format\n\n```\nSAST Pipeline Scan Report\n==========================\nRepository: org\u002Fweb-application\nBranch: feature\u002Fuser-auth-refactor\nScan Date: 2026-02-23\nCommit: a1b2c3d4\n\nCodeQL Results:\n  Language    Queries Run   Findings   Critical   High   Medium\n  javascript  312           4          1          2      1\n  python      287           2          0          1      1\n\nSemgrep Results:\n  Ruleset          Rules Matched   Findings   Errors   Warnings\n  auto             1,847           3          1        2\n  owasp-top-ten    186             2          1        1\n  custom-rules     12              1          0        1\n\nQUALITY GATE: FAILED\n  Blocking findings: 2 Critical\u002FHigh severity issues\n  - [CRITICAL] CWE-89: SQL Injection in src\u002Fapi\u002Fusers.py:47\n  - [HIGH] CWE-79: Cross-site Scripting in src\u002Fcomponents\u002FSearch.tsx:123\n\nAction Required: Fix blocking findings before merge is permitted.\n```\n",{"hide":55,"name":5,"source":56,"license":15,"description":7,"authorized_lab":51,"origin_frontmatter":57},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: integrating-sast-into-github-actions-pipeline | description: 'This skill covers integrating Static Application Security Testing (SAST) |   tools—CodeQL and Semgrep—into GitHub Actions CI\u002FCD pipelines. It addresses configuring |   automated code scanning on pull requests and pushes, tuning rules to reduce false |   positives, uploading SARIF results to GitHub Advanced Security, and establishing |   quality gates that block merges when high-severity vulnerabilities are detected. |  |   ' | d","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-integrating-sast-into-github-actions-pipeline",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-11 16:42:59",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":55},[68,71,74],{"tool":69,"command":70},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-integrating-sast-into-github-actions-pipeline",{"tool":72,"command":73},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-integrating-sast-into-github-actions-pipeline",{"tool":75,"command":76},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-integrating-sast-into-github-actions-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-integrating-sast-into-github-actions-pipeline\u002FSKILL.md",[],[80,102,126,154,183,202],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":50},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,42,99,40,100,101],"zoom out","zoom","with","harness","how","section","re","true","understand","use","perspective","you","it","context",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":50},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[109,110,91,111,112,113,114,115,116,117,118,97,119,42,120,121,122,123,124,125],"yuri shura","parallel","architecture review","planning","for","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":135,"publishedAt":50},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[136,137,138,139,140,141,142,143,144,42,145,146,147,148,149,150,151,113,152,153],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":168,"publishedAt":50},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[169,40,170,136,91,171,172,173,113,174,175,176,177,178,179,180,181,182,97,42],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":50},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[190,191,192,193,194,195,196,197,198,42,199,120,200,201],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":216,"publishedAt":50},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[208,209,212,213],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":214,"categoryName":215,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000036","内容创作者",[217,218,219,42,120,220,91,221,114,97,222],"writing","writing skills","new","work","editing","Existing"]