speclink-audit

Detect security vulnerabilities in code changes via simulated adversary perspectives.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speclink-audit
Source: https://github.com/MomoChenisMe/speclink/tree/main/.agents/skills/speclink-audit
Command: npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires speclink-cli, and includes scripts (resource) components.

What problem does it solve?

speclink-audit addresses the challenge of ensuring code security by automatically detecting potential security vulnerabilities in code changes.

Core Features & Use Cases

  • Security Analysis: Automates the detection of security issues in code such as dangerous defaults, type confusion, and silent failures.
  • Two Modes: Operates in 'Standalone' mode for detailed analysis and 'Discipline' mode during implementation for a quick checklist.
  • Adversary Analysis: Simulates the perspectives of a malicious actor, a lazy developer, and a confused developer to uncover security issues.
  • Use Case: For developers looking to enhance the security of their codebase by identifying and fixing potential vulnerabilities before deployment.

Quick Start

Run the speclink-audit skill to perform a security audit on the current changes in your codebase.

Frequently Asked Questions about speclink-audit

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

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

Automated security vulnerability detection in code changes is performed by simulating attacks from malicious, lazy, and confused developer perspectives to uncover issues like dangerous defaults and type confusion before deployment.

What types of security vulnerabilities can automated code analysis detect?

Automated code analysis detects security vulnerabilities such as dangerous defaults, type confusion, and silent failures. It simulates adversary perspectives to uncover these specific security issues within your codebase changes.

How does adversary analysis work for secure code review?

Adversary analysis for secure code review works by simulating attacks from three perspectives: a malicious actor, a lazy developer, and a confused developer. This simulation uncovers security issues that standard reviews might miss.

Do I need speclink CLI to run a security code review?

Yes, you need the speclink CLI installed to execute security code reviews. The audit skill requires this command-line interface dependency to analyze code changes and detect vulnerabilities.

When should I use Standalone mode versus Discipline mode for code analysis?

Use Standalone mode for detailed code analysis and Discipline mode during implementation for a quick security checklist. Both modes detect vulnerabilities but differ in analysis depth and workflow integration timing.

What is the best way to integrate vulnerability detection into a software engineering workflow?

The best way to integrate vulnerability detection into a software engineering workflow is running security audits on current codebase changes before deployment. This ensures compliance and identifies issues early through automated adversary simulation.