code-issues-find

Identifies scoped code bugs, security vulnerabilities, and contract violations in a repository.

2|Updated May 18, 2022

Search Tags:#static analysis #code review #security audit #software quality #bug detection #ledger

Ready to run

npx skills add https://github.com/alexfalkowski/bin --skill code-issues-find

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-issues-find
Source: https://github.com/alexfalkowski/bin/tree/main/skills/code-issues-find
Command: npx skills add https://github.com/alexfalkowski/bin --skill code-issues-find

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of identifying code bugs, security vulnerabilities, and contract violations in a structured, non-destructive manner without modifying the codebase.

Core Features & Use Cases

Scoped Issue Discovery: Systematically finds bugs, security flaws, and compatibility breaks within specific folders or packages.
Ledger-Based Workflow: Integrates with a centralized ledger to ensure findings are tracked, deduplicated, and actionable.
Use Case: Use this skill to perform a comprehensive audit of a newly integrated module to ensure it adheres to public contracts and security standards before deployment.

Quick Start

Trigger the code issues find skill by asking the agent to find code issues in the target package or folder.

Frequently Asked Questions about code-issues-find

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

FAQPage Schema

How do I find security vulnerabilities and code bugs in a specific package folder?▼

To find security vulnerabilities and code bugs in a specific package folder, you can trigger an audit by asking the agent to analyze the target directory. The skill systematically discovers scoped issues and generates actionable ledger entries for tracking without modifying the codebase.

What is a ledger-based workflow for static analysis and code review?▼

A ledger-based workflow for static analysis integrates findings into a centralized ledger to ensure identified code defects and risks are tracked, deduplicated, and actionable. This approach maintains a structured, non-destructive record of security vulnerabilities and contract violations for subsequent implementation.

Does this code review process check for public-contract violations and compatibility breaks?▼

Yes, this code review process explicitly checks for public-contract violations and compatibility breaks. It operates by analyzing code, tests, and documentation to identify these issues alongside security flaws and bugs, generating high-confidence findings that adhere to defined audit rules.

Can I use this security audit on a newly integrated module before deployment?▼

Yes, you can perform a comprehensive security audit on a newly integrated module before deployment. This ensures the module adheres to public contracts and security standards, providing a structured assessment of code defects and compatibility breaks within the scoped package.

What are the limitations of running a non-destructive code issue audit?▼

The primary limitation of this non-destructive code issue audit is that it does not modify the codebase to fix the identified defects. It strictly generates ledger entries for subsequent implementation, meaning users must separately address the discovered bugs, security vulnerabilities, and compatibility breaks.