MAJI-Skills

Generate concise documentation from code. README, function docs, API references, architecture notes — written in plain language, with examples that work, no padding. Use when shipping or onboarding and you want docs that read fast and stay accurate.

Scope-guarded refactoring. Define target → identify minimum diff → preserve behaviour → verify with tests. Pre-Action Gate prevents scope drift into unrelated improvements. Use when you want a targeted refactor that does not turn into a 50-file rewrite.

Compress long content into structured summary. TLDR + key points + action items, length-tunable. Use for meeting notes, transcripts, long docs, threads, codebases. No padding, no editorial commentary.

Generate disciplined test cases. Focus on behaviour not implementation, cover edge cases without bloat, name tests for the case not the function. Use when writing tests for new code or filling gaps in coverage.

Extract and triage TODO/FIXME/HACK comments from a codebase. Categorize by urgency, group by file, identify stale TODOs older than threshold. Use during cleanup sprints, before releases, or when onboarding a new project.

Generate a concise commit message from the current git diff. Conventional commits format (feat/fix/refactor/etc). Use when staged changes are ready to commit and you want Claude to write the message instead of typing it manually.

Disciplined debug session protocol. Read symptom → form hypothesis → verify before fixing → propose minimum-change fix. Pre-Action Gate prevents hasty rewrites that break unrelated code. Use when an error or unexpected behaviour appears and you want a focused diagnosis instead of guess-and-check.

Concise code or concept explainer. Lead with one-sentence answer, then layered detail only if useful. No padding, no "let me walk you through". Use when encountering unfamiliar code, library, error message, or concept and you want fast comprehension instead of a textbook lecture.

A Claude collaboration discipline. Lead with outcome+constraint, identify decision modes (discuss/build/pause/pivot), recognize frustration signals, enforce Pre-Action Gate before risky operations. Type "verify maji-mode" to confirm active state. Use when starting any session to ship faster with less rework.

Disciplined code review skill. Outputs structured feedback grouped by severity (critical/important/style/suggestion) with file:line references. No preamble, no padding, evidence-first. Use when reviewing a PR, diff, or file and you want focused actionable feedback instead of a wall of comments.