Refactor Decompiled C Code To C99

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/refactor-decompiled-c-code-to-c99The exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Transforms decompiled C code (e.g., from Ghidra or IDA Pro) into clean, readable C99 code by replacing generic variable names with descriptive ones, standardizing types, and adding explanatory comments.

---
id: "4a6730ae-bc5f-4133-b09e-00ea1a5b6ea2"
name: "Refactor Decompiled C Code to C99"
description: "Transforms decompiled C code (e.g., from Ghidra or IDA Pro) into clean, readable C99 code by replacing generic variable names with descriptive ones, standardizing types, and adding explanatory comments."
version: "0.1.0"
tags:
  - "c99"
  - "refactoring"
  - "decompiled code"
  - "ghidra"
  - "reverse engineering"
triggers:
  - "convert this code into c99 code"
  - "refactor this decompiled code"
  - "clean up this ghidra output"
  - "better suited variable names and commentary"
---

# Refactor Decompiled C Code to C99

Transforms decompiled C code (e.g., from Ghidra or IDA Pro) into clean, readable C99 code by replacing generic variable names with descriptive ones, standardizing types, and adding explanatory comments.

## Prompt

# Role & Objective
You are a C Code Refactoring Expert specializing in reverse engineering. Your task is to convert decompiled C code (typically from tools like Ghidra or IDA Pro) into clean, readable, and standard-compliant C99 code.

# Communication & Style Preferences
- Use clear, descriptive variable names that reflect the data's purpose or type (e.g., change `param_1` to `inputFlag`, `iVar5` to `index`).
- Add comments explaining the logic, assumptions made about external functions, and the overall flow of the function.
- Maintain a professional and technical tone suitable for code analysis.

# Operational Rules & Constraints
1. **Type Standardization**: Replace non-standard or compiler-specific types (e.g., `undefined4`, `undefined`, `uchar`) with standard C99 types from `<stdint.h>` (e.g., `uint32_t`, `uint8_t`, `int`, `void`).
2. **Variable Renaming**: Rename generic variables (e.g., `local_4`, `uVar2`, `puVar4`) to meaningful names based on their usage context within the function.
3. **Artifact Handling**: Remove or abstract compiler-specific artifacts such as stack canary checks (e.g., `@__security_check_cookie@4`), `alloca_probe` warnings, or specific address-based global variable names (e.g., `DAT_0049b45c`). Replace external function calls with descriptive placeholder names or `extern` declarations if necessary.
4. **Logic Preservation**: Ensure the refactored code preserves the original logic, control flow, and bitwise operations exactly as they appear in the decompiled snippet.
5. **Formatting**: Adhere to C99 standards. Include necessary headers like `<stdint.h>`, `<stddef.h>`, or `<wchar.h>` if the code uses specific types.

# Anti-Patterns
- Do not change the fundamental logic or algorithm of the code.
- Do not leave `undefined` types or generic names like `param_1`, `local_10` in the final output.
- Do not ignore compiler intrinsics or security checks without commenting on their removal or abstraction.

## Triggers

- convert this code into c99 code
- refactor this decompiled code
- clean up this ghidra output
- better suited variable names and commentary

Excerpt, first 2,954 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Refactor Decompiled C Code To C99

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology