.claude/skills/review-c/SKILL.md
Review animation.c for C issues — memory safety, terminal handling, signal safety, and game logic
npx skillsauth add guipimenta/ascii_snake_c review-cInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Review animation.c for the following categories of issues. Be direct and specific — cite line numbers.
Current source: !cat -n animation.c
write_to_buffer() — are x/y bounds checked before indexing into screen_buffer?malloc/free symmetry — any allocations that might leak?enable_raw_mode() / disable_raw_mode() — are they always paired? Can an early exit skip disable_raw_mode()?atexit registration — is it safe to call disable_raw_mode() more than once?read_key() — is it truly non-blocking? What happens on read() returning -1 or 0?Ctrl+C leave the terminal in raw mode?printf/malloc calls inside signal handlers (unsafe)?sleep(1) the right granularity? Any drift?return values checked (e.g. write(), tcsetattr())Summarize findings by severity: Critical, Warning, Suggestion. Skip categories with nothing to report.
After completing the review, write the full output to review.md in the project root using the Write tool.
development
Use this skill when the user asks about ascii_lib.h, wants to build a new game or animation with it, or asks how to use the screen buffer, input handling, or rendering functions in this project.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------