roast-my-code
openbooklet.com/s/roast-my-codeopenbooklet.com/s/roast-my-code@1.0.0GET /api/v1/skills/roast-my-codeUse when user wants a brutally honest code roast, quality critique, or AI-readiness audit. Use when user says roast, roast my code, critique my code, tear apart my code, review quality, or AI-readiness check. Supports --fix flag to auto-fix CRITICAL and HIGH issues via core-dev workflow.
Use when the user wants to benchmark or compare AI agents (Claude Code, Codex, OpenCode) on a refactoring, perf, or code-change task in the current repo. Use when user says compare agents, benchmark Claude vs Codex, agent eval, measure agent, AI agent comparison, agent trial, /ai-agent-bench.
Use when user wants to align docs with the current project status or new discoveries
Use when starting a new development task to capture context, or when finalizing a task to document discoveries and decisions.
Use when user asks to transfer session context to a new chat, summarize current state for a handoff, hand off work, or runs /context-transfer. Produces a structured handoff document (summary, decisions, gotchas, relevant files, current state, ready-to-paste prompt).
Use when any coding, development, analysis, debugging, or code-related task is detected. Triggers on: implementing features, fixing bugs, refactoring code, reviewing diffs, investigating errors, evaluating approaches, or making architecture decisions.
Use when user wants to design tests, analyze test coverage quality, generate boundary/property/invariant tests, audit existing tests for weak assertions, or create golden fixture capture scripts. Use when user says create test, design tests, test strategy, what should I test, explore tests, test quality, boundary testing, fuzz testing, property-based testing, golden fixtures, or /create-test.
Use when user says regression test, eval check, eval regression, test before commit, compare versions, check regressions, run evals, benchmark skill, or /eval-regression. Compares current (modified) version against last committed version to detect regressions, improvements, and behavioral changes.
Java development. Use for Java, Spring Boot, Maven, Gradle, JPA, Hibernate.
Use when user wants to produce a factual chronicle of development-skills plugin interactions in the current conversation for later ingestion, or runs /produce-feedback. Pure record, no judgment.
Use when the user asks to resolve merge conflicts, fix a failed merge, rebase conflict, or run /resolve-merge. Use when git status shows UU/AA/DD conflicts, when there are <<<<<<< conflict markers, when git merge or git pull failed with CONFLICT, or when numbered docs/plans need renumbering after merge. Triggers on: merge conflict, conflict markers, both modified, git merge failed, rebase conflict, resolve conflicts.
Swift development. Use for Swift, SwiftUI, UIKit, Vapor, SPM, XCTest, Combine.
TypeScript development. Use for TypeScript, Node.js, Express, Fastify, Zod, vitest, jest. Backend, CLI, libraries only â no frontend frameworks.
Use when user wants to update .pre-commit-config.yaml hooks to their latest versions from GitHub
Use when user wants to update requirements.in with latest PyPI versions while preserving version patterns
Use when user wants to update requirements-dev.in with latest PyPI versions while preserving version patterns
Auto-indexed from reidemeister94/development-skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.