Claude Skills by reidemeister94

Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.

Explain a diff, branch, PR, patch, or review packet; use after Full-path verification when the change teaches a useful business or technical concept.

Create a self-contained temporary handoff document when the user asks to transfer the session to a new chat or runs /handoff.

Produce factual development-skills feedback or ingest a report to apply only evidence-backed simplifications.

Deep simplification pass over a target's files. Use when the user invokes /simplify-stuff or asks to simplify files, docs, skills, or plugins (simplify, semplifica).

Run a factual, staff-level review of a local branch, diff, repo, directory, or file. Use for code review, deep review, review-my-changes, or staff-review requests.

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 the user wants state-of-the-art knowledge, best practices, or evidence-based analysis of ANY topic — technology, health, fitness, nutrition, finance, design, psychology, architecture, productivity, learning, or any field where humanity has accumulated knowledge. Use when user says best practices, state of the art, most effective, optimal, evidence-based, how should I, what's the best way to, pros and cons, comparison, or /best-practices.

Use when creating features, building components, adding functionality, modifying behavior, designing systems, choosing between approaches, or making architectural decisions.

Use when starting a new development task to capture context, or when finalizing a task to document discoveries and decisions.

Use when user wants to make a project's agent context compatible with both Claude Code and Codex CLI and AGENTS.md standards

Use when the user asks to commit changes, create a commit, or run /commit. Use when staged changes need a conventional commits message.

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 create tests, generate test coverage, audit test quality, find untested code, or improve weak assertions. Use when user says write tests, test coverage, missing tests, or untested code.

Use when fixing bugs, investigating errors, debugging failures, or diagnosing unexpected behavior.

Use when user wants to reduce noise, verbosity, or redundancy in markdown or text files. Use when user says distill, compress, clean up, tighten, denoise, reduce entropy, improve signal-to-noise ratio, or make text more concise. Accepts a file path, a directory (distills all .md/.txt files in it), or no argument (distills all .md/.txt files in the current directory).

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.

Frontend development. Use for React, Next.js, Raycast extensions, Vite-based frontend projects.

Use when user wants to ingest a development-skills feedback report and apply fixes, or runs /ingest-feedback. Challenges every suggestion against Core Pillars before accepting; most friction points should SKIP. Expect a report path as argument.

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.

Python development. Use for Python, FastAPI, Pydantic, asyncpg, pytest, pandas, SQLAlchemy.

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.

Use 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.

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-dev.in with latest PyPI versions while preserving version patterns

Use when user wants to update requirements.in with latest PyPI versions while preserving version patterns

Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first.