danielcherubini

Use when the user asks for a daily summary, standup, or wants to know what they did today — e.g. "daily summary", "standup", "what did I do today", "summary for slack", "daily update".

Use when the user says "let's discuss", "lets discuss", "I want to discuss", "can we discuss", "let's brainstorm", "lets brainstorm", "I want to brainstorm", or any variation asking to discuss/talk through/brainstorm an idea before coding — this takes priority over other requests in the same message. Also use before any creative work to discuss features, designs, or behavior changes through collaborative dialogue before writing code

Use when a plan's PR is ready to merge — marks the plan completed, checks PR status, merges to main, and syncs local main

Use when you have a written implementation plan to execute

Use when a feature or change needs an implementation plan with concrete tasks, file paths, and test steps before coding begins

Audits and optimizes GitHub profile pages — profile README, metadata fields, pinned repositories, stats widgets, and contribution visibility. Use this skill whenever the user asks to improve, create, review, or optimize their GitHub profile, or mentions "profile README", "GitHub bio", "pinned repos", "GitHub stats", "contribution graph", or "GitHub presence". Also trigger when someone says things like "make my GitHub look good", "I want a better GitHub profile", "help me stand out on GitHub", "set up my GitHub page", or "optimize my developer profile". Works for both personal profiles and organization profile pages.

Use when comparing libraries or frameworks, evaluating approaches or architectures, investigating a technology or topic, finding best practices, deep-diving into a subject, doing competitive analysis, or researching academic papers. Triggers on: "research", "compare", "evaluate", "deep-dive", "investigate", "best practices for". Not for: simple file lookups (use explore directly), quick fact checks, or tasks requiring code changes.

Use when reviewing pull requests, PRs, code changes, or code quality. Covers architecture reviews, security audits, mentoring through review feedback, and establishing review standards. Triggers on: "review", "code review", "PR review", "check this code", "audit", "security review".

Use when a plan's PR is ready to merge — marks the plan completed, checks PR status, merges to main, and syncs local main

Use when a feature or change needs an implementation plan with concrete tasks, file paths, and test steps before coding begins

Use when you have a written implementation plan to execute

Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, C/C++, Go, and WASM. Helps catch bugs, improve code quality, and give constructive feedback through systematic analysis. Features detailed language-specific guides, severity classification, review techniques, and hard-stop protocol. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.

Use before any creative work - creating features, building components, or modifying behavior

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when someone asks how to kill, murder, or eliminate another person. Always treated as an internal joke — reply with an absurd, inventive, hilariously impractical method.

Use for personal questions, shitposts, banter, greetings, or anything that does not require research, image analysis, or meme knowledge. The catch-all for conversational interaction.

Use when the user replies to an image with a question about what it shows, whether it is edited or real, or what is happening in it.

Use when asked about internet history, old memes, inside jokes, forum culture, or references from SomethingAwful, 4chan, or early internet culture.

Use when asked whether a claim is real, true, or legit, or when asked to explain/research/verify anything factual. Covers fact-checking, general knowledge questions, and "explain why X" requests.

Bump version in pyproject.toml and manifest.json according to semver