skills.rest
Alexmacapple
AlexmacappleCOMMUNITY
Explore all skills by this author →
GitHub

raisonnement-code

Enforce line-referenced, 7-step proof-based code reviews with formal verdicts.

1|Updated Apr 5, 2026
Search Tags:#verification#reasoning#traceability#patch#code-review#semi-formal
One-click install
npx skills add https://github.com/Alexmacapple/alex-claude-skill --skill raisonnement-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: raisonnement-code
Source: https://github.com/Alexmacapple/alex-claude-skill/tree/main/raisonnement-code
Command: npx skills add https://github.com/Alexmacapple/alex-claude-skill --skill raisonnement-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enforces a proof-based review of code by requiring citations to exact file:line references for every claim, eliminating guesswork in patch, bug, and QA analyses.

Core Features & Use Cases

  • Explicitly formats reviews as 7-step semi-formal analyses (reformulation, premises, scope, trace, data flow, hypotheses, conclusion).
  • Supports three modes (patch, bug, qa) to locate defects, verify patches, or answer behaviour questions with evidence.
  • Useful for rigorous code reviews, migrations validations, and educational demonstrations of reasoning.

Quick Start

To start a semi-formal review, provide a code patch and request a structured analysis via /raisonnement-code patch.

Frequently Asked Questions about raisonnement-code

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

FAQPage Schema
How do I verify a code patch with line references instead of guessing?▼

Patch verification with line references requires providing source files and diffs to generate a 7-step semi-formal analysis, outputting explicit premises, data flow, trace references, and a formal verdict.

What is semi-formal code reasoning and how does it help bug localization?▼

Semi-formal code reasoning enforces verifiable, line-referenced proofs for every assertion to locate bugs, eliminating guesswork by mapping explicit premises and data flow to a deterministic trace and formal conclusion.

How do I get an evidence-based QA analysis for my codebase behavior?▼

Getting an evidence-based QA analysis for codebase behavior requires submitting behavior questions alongside source files to generate structured reasoning with file:line trace references and a formal verdict.

Can I use a structured 7-step analysis for migration validation?▼

You can use the 7-step analysis for migration validation by processing diffs through reformulation, scope, trace, data flow, hypotheses, and a formal conclusion to rigorously verify changes across diverse codebases.

Do I need to provide source files to get a verifiable code review?▼

You need to provide source files and diffs to get a verifiable code review, as the analysis requires deterministic trace references to exact file:line citations for every assertion and formal conclusion.

When should I not use semi-formal reasoning for code reviews?▼

You should not use semi-formal reasoning for code reviews when you lack access to source files and diffs, as the 7-step analysis strictly requires deterministic trace references to generate verifiable proofs and formal verdicts.

Related Skills

Explore More Software Engineering Skills→
LuminairPrimeLuminairPrime
1

code-reviewer

Analyze edited source files for style, bug, and security issues.

Community
Intermediate
knot0-comknot0-com
9

semi-formal-reasoning

Enforce explicit premises and file:line traces in code analysis.

Official
Advanced
julianobarbosajulianobarbosa
7

reviewing-code

Review code for quality, bugs, security issues, and best practices using Codex.

Community
Advanced
mytechsonamymytechsonamy
1

consensus-specialist

Dispatch phase-specific specialists to rewrite artifacts and generate patch files.

Community
Advanced