nim-defect-analysis

Trace externally controlled inputs to missing guards in Nim code.

Updated Aug 27, 2026

Search Tags:#code review #reliability #nim #defect analysis #ffi safety #async io #static tracing

Ready to run

npx skills add https://github.com/planetis-m/skills_experiment --skill nim-defect-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nim-defect-analysis
Source: https://github.com/planetis-m/skills_experiment/tree/main/skills/nim-defect-analysis
Command: npx skills add https://github.com/planetis-m/skills_experiment --skill nim-defect-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and classify real reliability defects in Nim code before they become crashes, data corruption, or resource failures.

Core Features & Use Cases

Deterministic defect triage: Map boundaries, enumerate high-signal risk sites, and generate bounded hypotheses instead of broad speculation.
Evidence-gated confirmation: Classify findings as CONFIRMED only when a reproducer or equivalent artifact supports the failure and root cause.
Root-cause and remediation reporting: Provide expected vs actual behavior, static trace details, impact assessment, and an actionable remediation direction.

Quick Start

Ask the AI to run nim-defect-analysis on your Nim source file to produce a short, evidence-based report of reliability defects and their root causes.

Frequently Asked Questions about nim-defect-analysis

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

FAQPage Schema

How do I find reliability defects in Nim code before runtime crashes?▼

Nim defect analysis identifies reliability defects by tracing externally controlled inputs to missing guards and failure paths. It classifies findings using evidence-gated confirmation with static traces, requiring reproducer artifacts to confirm root causes.

What is the best way to review FFI boundaries for missing guards in Nim?▼

FFI boundary review in Nim benefits from deterministic defect triage that maps boundaries and enumerates high-signal risk sites. This generates bounded hypotheses with static traces to pinpoint robustness failures escaping typical error handling.

Can I use static tracing to check async I/O handlers for failure paths?▼

Static tracing applies to async I/O handlers by mapping externally controlled inputs to their failure paths. It provides bounded hypotheses and optional minimal reproducers to verify robustness failures without executing the asynchronous runtime.

Does Nim defect analysis work for ownership and destroy hooks?▼

Nim defect analysis targets ownership, copy, and destroy hooks where robustness failures escape typical error handling. It requires evidence-gated classification, confirming defects only when reproducer artifacts support the identified root cause.

How do I verify Nim parser defects without broad speculation?▼

Parser defect verification uses deterministic defect triage to map boundaries and enumerate risk sites, generating bounded hypotheses. Findings are classified as confirmed only when supported by equivalent artifacts and static traces.

What are the limitations of evidence-gated defect classification in Nim?▼

Evidence-gated defect classification limitations require a reproducer or equivalent artifact to confirm failures. Without static traces or bounded hypotheses supporting the root cause, findings remain unconfirmed and speculative.