Guidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the logic".
Reviews engineering blog drafts. Use this skill whenever the user says "ape review blog", "review blog", "review this post", "give feedback on draft", "what is wrong with this post", or pastes a blog draft asking for critique, feedback, or editorial review. Also trigger when the user shares a draft and asks if it is ready to publish. Always use this skill for any engineering blog review request, even if the user just says "thoughts?" after pasting a post.
Rewrites an engineering blog draft by first running the ape-review-blog skill on it and then applying every suggested fix to produce a revised version. Use this skill whenever the user says "ape rewrite blog", "rewrite blog", "rewrite this post", "apply review suggestions", "fix the draft", "rewrite the draft", or shares a blog file and asks to apply review feedback. Also trigger when the user has already received a review and wants the suggestions implemented in a new file. Always use this skill for any engineering blog rewrite request where the goal is to produce a fixed-up draft, not just a review. The rewrite is written to a sibling file with the `-ape.md` suffix.
A surgical editor that strips fluff and redundant information out of a piece of writing and drives the word count down to the bare minimum needed to convey the concept. Flags and removes hedging, empty disclaimers, throat-clearing intros, cliché openers, empty subject openers, filler transitions, self-reference and meta-structure, summarising conclusions, rhetorical-question tails, intro-body-conclusion symmetry, padded constructions, nominalisations, filler qualifiers, adjective and intensifier stacks, redundant pairs, restatement and cross-paragraph repetition, redundant examples and analogies, redundant background and context, redundant elaboration, dead sentences, AI-slop framing, code-narration, ceremonial closers, and non-load-bearing filler words (articles, auxiliaries, connective tissue) whose removal does not change meaning. Use this skill whenever the user says "ape cut fluff", "cut the fluff", "trim this", "tighten this", "strip the fluff", "make this crisp", "remove filler", "remove redundancy", "
Apply consistent, professional Markdown formatting rules whenever producing or reformatting Markdown output. Use this skill when generating any Markdown document, when the user asks to reformat or clean up existing Markdown, when producing README files, technical docs, notes, or any other content that will be rendered as Markdown. Trigger even when the request seems simple -- any Markdown output should follow these rules. Do not use this skill for non-Markdown outputs such as plain text, HTML, or code-only responses.
Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".