bk-scan

Detect security and compliance issues in code repositories using pattern matching and rule sets.

22|17|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/dandacompany/bluekiwi --skill bk-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bk-scan
Source: https://github.com/dandacompany/bluekiwi/tree/main/packages/cli/src/assets/skills/bk-scan
Command: npx skills add https://github.com/dandacompany/bluekiwi --skill bk-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection of security vulnerabilities and compliance risks within code repositories, reducing manual review efforts and enhancing software security.

Core Features & Use Cases

  • Automated Pattern Analysis: Scans local repositories for known security and compliance issues based on predefined rule sets.
  • Customizable Scans: Allows users to define specific scan parameters, including custom rule configurations.
  • Use Case: Developers can automatically identify hardcoded secrets or high-risk PII in project files before deployment, ensuring code safety and regulatory adherence.

Quick Start

Ask the AI to initiate a security scan on your project directory, review the findings, and decide whether to attach these to a task for further remediation.

Frequently Asked Questions about bk-scan

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

FAQPage Schema
How do I automate security vulnerability detection in my code repository?

Automating security vulnerability detection in a code repository requires scanning local files using pattern matching and predefined rule sets. This Skill automates that detection process to identify hardcoded secrets and high-risk PII before deployment.

Can I use custom rule configurations for compliance scanning?

Yes, you can use custom rule configurations for compliance scanning by defining specific scan parameters. This allows the static analysis to adapt to various security standards and regulatory requirements within your project files.

How do I scan local repositories for hardcoded secrets and PII?

Scanning local repositories for hardcoded secrets and PII involves running automated pattern analysis against your project directory. You can ask the AI to initiate a security scan to automatically identify these risks and review the findings.

What is static analysis for compliance audits in software development?

Static analysis for compliance audits is the process of scanning code repositories without executing the program to detect security vulnerabilities. It uses configurable rule parameters to ensure software adheres to regulatory standards.

Do I need static analysis tools to run repository security scans?

Yes, you need static analysis tools to run repository security scans. These tools provide the foundational pattern matching capabilities required to execute the rule sets and detect compliance risks within your code.

How do I review security scan findings and attach them to a remediation task?

Reviewing security scan findings involves analyzing the detected vulnerabilities from your project directory scan. After the AI generates the findings, you can decide whether to attach these results to a task for further remediation.