all publishers

MrCipherSmith

@mrciphersmith source repo

178 published skills · page 1 of 2

  1. ▌
    Code Verifier 4 · mrciphersmith bundle
    Use when running a full quality gate after implementation — lint, type-check, tests, and import validation. Mandatory step in job-orchestrator after task-implementer and after fix iterations. Use standalone when you need a structured verification report.
    0 repo stars
  2. ▌
    Review Orchestrator · mrciphersmith bundle
    Use when: a code review is requested and the user does not explicitly name a specialized reviewer. Handles "review", "code review", "review PR", "review --frontend", "review --backend", "review --architecture", "review --security", "review --performance", "review --style", "review --strict", "review --project-conventions", "review --legacy-profiles", "review --all". Routes to specialized reviewers in parallel and consolidates findings into one unified report. NOT for: running a single specialized reviewer — invoke it directly by name instead.
    0 repo stars
  3. ▌
    Code Verifier · mrciphersmith bundle
    Use when running a full quality gate after implementation — lint, type-check, tests, and import validation. Mandatory step in job-orchestrator after task-implementer and after fix iterations. Use standalone when you need a structured verification report.
    0 repo stars
  4. ▌
    Job Orchestrator 2 · mrciphersmith bundle
    Use when a GitHub issue or complex intent needs to be analyzed, planned, and implemented end-to-end with sub-agents.
    0 repo stars
  5. ▌
    Review Orchestrator 3 · mrciphersmith bundle
    Use when: a code review is requested and the user does not explicitly name a specialized reviewer. Handles "review", "code review", "review PR", "review --frontend", "review --backend", "review --architecture", "review --security", "review --performance", "review --style", "review --strict", "review --project-conventions", "review --legacy-profiles", "review --all". Routes to specialized reviewers in parallel and consolidates findings into one unified report. NOT for: running a single specialized reviewer — invoke it directly by name instead.
    0 repo stars
  6. ▌
    Review UI UX · mrciphersmith
    Use when: reviewing UI changes or a live page/screen for UX quality and AI-slop — usability heuristics, system states, forms, visual hierarchy, WCAG 2.2 AA, craft thresholds, and the generic "AI-generated look". Works on a diff (code mode) and on a running URL or screenshots (live mode). Triggers: "UI review", "UX review", "ревью UI/UX", "looks like AI slop?", "review --ui-ux", or dispatched by review-orchestrator for --ui-ux, --all, or diffs touching *.tsx, *.jsx, *.vue, *.svelte, *.css, *.scss, *.html. NOT for: React/MobX structure (review-frontend), naming and readability (review-style), re-render cost (review-performance), repository class conventions (review-frontend-conventions), or choosing/building a new design (ui-direction, ui-craft).
    0 repo stars
  7. ▌
    UI Direction · mrciphersmith
    Use when: a new page, screen, product, or redesign needs a visual concept BEFORE any UI code is written, or when existing UI "looks generic / AI-made / like every other SaaS" and needs a distinctive direction. Produces a persistent DESIGN.md (concept sentence, palette, type, layout wireframes, motion stance, signature element, not-doing list) that ui-craft builds from and review-ui-ux reviews against. Triggers: "design direction", "make it unique", "не нейрослоп", "придумай визуальный концепт", "redesign the look", "/ui-direction". NOT for: writing the components (ui-craft), reviewing existing UI (review-ui-ux), or token/component-library maintenance in an established design system (design:design-system).
    0 repo stars
  8. ▌
    Doubt Driven Development · mrciphersmith
    Use when a non-trivial decision is about to stand — branching logic, cross-boundary change, unverifiable invariant, or irreversible blast radius — and you want a fresh-context adversarial reviewer to catch a wrong direction in-flight, while correction is still cheap. NOT for mechanical edits, one-liners, or explicit user instructions.
    0 repo stars
  9. ▌
    Constraint Driven Development · mrciphersmith
    Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
    0 repo stars
  10. ▌
    UI Craft · mrciphersmith
    Use when: building or restyling UI (page, screen, component set) and the result must look designed rather than AI-generated — tokens first, real content, every state, purposeful motion, WCAG 2.2 AA, verified in a real browser. Builds from DESIGN.md (run ui-direction first when none exists). Stack-agnostic: adapts to the project's Tailwind / CSS modules / component library. Triggers: "build this page", "сверстай", "make this UI look good", "implement the design", "restyle", "/ui-craft". NOT for: choosing the visual concept (ui-direction), reviewing a diff (review-ui-ux), React/MobX architecture (review-frontend), or measuring layout regressions (review-layout).
    0 repo stars
  11. ▌
    Review Clean Code 2 · mrciphersmith
    Use when: reviewing code against Clean Code principles (Uncle Bob) and SOLID at the function/class level — meaningful names, small functions, single level of abstraction, argument count, error handling, DRY, comment quality, and SOLID (SRP, OCP, LSP, ISP, DIP) as applied to individual classes and functions. Triggered by: "review clean code", "check clean code", "Uncle Bob review", "SOLID review", "review --clean-code", or dispatched by review-orchestrator. NOT for: architectural layer violations (review-architecture), naming convention formatting (review-style), logic correctness bugs (review-logic), or security (review-security-code).
    0 repo stars
  12. ▌
    Context Collector 3 · mrciphersmith bundle
    Use when a job needs a unified context document — gathering docs, libraries, and references for sub-agents before execution.
    0 repo stars
  13. ▌
    Review Testing Practices 2 · mrciphersmith bundle
    Use when reviewing unit, integration, Storybook, component, or e2e tests against repository-local testing conventions: co-location, network mocking, MSW-style boundary mocks, behaviour assertions, deterministic waits, smoke/full split, locator priority, and screenshot-test discipline. Dispatched by review-orchestrator for --testing-practices, --project-conventions, --all, or changed test/e2e/story files.
    0 repo stars
  14. ▌
    Gproject Consistency Checker 2 · mrciphersmith bundle
    Validates PRD/Implementation Plan against decisions registry, architecture doc, and best practices constraints. Catches contradictions, gaps, and violations. Use when: dispatched by gproject-orchestrator Phase 5. NOT for: direct user invocation.
    0 repo stars
  15. ▌
    Gproject Patterns Researcher 2 · mrciphersmith bundle
    Researches best practices per technology in the chosen stack and defines application architecture patterns. Produces constraints that PRD must follow. Use when: dispatched by gproject-orchestrator Phase 3. NOT for: direct user invocation.
    0 repo stars
  16. ▌
    Pr Issue Documenter 3 · mrciphersmith bundle
    Use when documenting PR changes, adding a PR description, creating a linked issue for a PR, or updating an existing issue body.
    0 repo stars
  17. ▌
    Review Frontend Conventions 2 · mrciphersmith bundle
    Use when reviewing frontend code against repository-local conventions commonly captured in CLAUDE.md or similar project guides: React/MobX boundaries, TypeScript strictness, i18n placement, storage wrappers, error handling, styling tokens, Storybook expectations, and local tooling rules. Dispatched by review-orchestrator for --frontend-conventions, --project-conventions, --all, or frontend src/**/*.ts(x) changes when local convention docs exist.
    0 repo stars
  18. ▌
    Issue Analyzer 2 · mrciphersmith bundle
    Use when decomposing a GitHub issue into atomic tasks for AI implementation, planning task breakdown, or preparing work for task-implementer agents.
    0 repo stars
  19. ▌
    Pr 2 · mrciphersmith bundle
    Use when opening a pull request for the current branch.
    0 repo stars
  20. ▌
    Iago 2 · mrciphersmith bundle
    Use when generating or updating a Mermaid diagram for a GitHub pull request review, especially after reviewing a diff and needing to explain control flow, sequence, classes, or entity relationships. Triggered by: iago, /iago, /squawk, generate PR diagram, add Mermaid diagram to PR, or visualize this review.
    0 repo stars
  21. ▌
    Push 2 · mrciphersmith bundle
    Use when pushing the current branch to the remote, especially when upstream tracking or safety checks are needed.
    0 repo stars
  22. ▌
    Commit 2 · mrciphersmith bundle
    Use when committing code changes and a well-structured conventional commit message is needed, with optional amend or selective staging.
    0 repo stars
  23. ▌
    Deploy 2 · mrciphersmith bundle
    Use when deploying to any environment (staging, production) or when a deployment pipeline needs to run.
    0 repo stars
  24. ▌
    Hookify 2 · mrciphersmith bundle
    Use when adding automated hook behavior to Claude Code or Cursor from a natural language description.
    0 repo stars
  25. ▌
    Changelog 2 · mrciphersmith bundle
    Use when generating a changelog, release notes, or summarizing what changed between tags, versions, or date ranges.
    0 repo stars
  26. ▌
    DB Migrate 2 · mrciphersmith bundle
    Use when creating, applying, rolling back, or checking the status of database migrations.
    0 repo stars
  27. ▌
    Brd Creator 2 · mrciphersmith bundle
    Use when a user request needs to be transformed into a Business Requirements Document (BRD) capturing business context, stakeholders, and success metrics.
    0 repo stars
  28. ▌
    Code Review 2 · mrciphersmith bundle
    Comprehensive code review with 4 parallel agents: correctness/logic, security, performance, style/maintainability. Produces unified severity report (CRITICAL/HIGH/MEDIUM/LOW). Use for thorough PR reviews and pre-merge checks.
    0 repo stars
  29. ▌
    Feature Dev 2 · mrciphersmith bundle
    Use when taking a feature from idea or GitHub issue all the way to a merge-ready PR in one guided workflow.
    0 repo stars
  30. ▌
    Fsd Creator 2 · mrciphersmith bundle
    Use when PRD and BRD exist and need to be expanded into a Functional Specification Document (FSD) detailing feature behavior, UI states, logic rules, and interface contracts.
    0 repo stars
  31. ▌
    Trd Creator 2 · mrciphersmith bundle
    Use when PRD and FSD exist and need to be expanded into a Technical Requirements Document (TRD) covering architecture, tech stack, data models, API contracts, and non-functional requirements.
    0 repo stars
  32. ▌
    Caveman Mode 2 · mrciphersmith
    Use when the user wants all AI responses in the current session to be terse and token-efficient. Activates caveman-mode: no preamble, no filler, fragments over sentences, bullets over prose.
    0 repo stars
  33. ▌
    Review Logic 3 · mrciphersmith bundle
    Use when: reviewing code for logic correctness, algorithmic bugs, missing error handling, async/await mistakes, null/undefined risks, race conditions, type contract violations, or spec compliance. Dispatched by review-orchestrator for --frontend, --backend, and --all. Also invoked directly: "review logic", "check correctness", "are there any bugs here". NOT for: security vulnerabilities, performance profiling, style/naming preferences, or architectural pattern concerns — those belong in their respective specialized reviewers.
    0 repo stars
  34. ▌
    Autodoc Writer 2 · mrciphersmith bundle
    Phase 4 subagent for autodoc-orchestrator. Writes one documentation section from analysis artifacts. Dispatched in parallel — one instance per section. Use when: dispatched by autodoc-orchestrator Phase 4. NOT for: direct user invocation.
    0 repo stars
  35. ▌
    Code AI Review 2 · mrciphersmith bundle
    Performs strict AI code review following code-review-ai-assistant.mdc standards. Reviews current branch changes from merge-base by default, including both committed and local uncommitted changes. Use when: code review requested, checking branch changes, reviewing implementation quality.
    0 repo stars
  36. ▌
    Autodoc Analyst 2 · mrciphersmith bundle
    Phase 2 subagent for autodoc-orchestrator. Deep-dives into a single module to extract purpose, structure, public API surface, patterns, and key dependencies. Use when: dispatched by autodoc-orchestrator Phase 2 (one instance per module). NOT for: direct user invocation.
    0 repo stars
  37. ▌
    Autodoc Scanner 2 · mrciphersmith bundle
    Phase 1 subagent for autodoc-orchestrator. Scans project structure, detects stack, identifies module boundaries, entry points, and dependencies. Use when: dispatched by autodoc-orchestrator Phase 1. NOT for: direct user invocation.
    0 repo stars
  38. ▌
    Code Boss Review 2 · mrciphersmith bundle
    Performs strict boss-style code review following code-review-boss-profile.mdc. Reviews current branch changes from merge-base. Direct, no-fluff feedback focused on logic correctness. Use when: boss review requested, strict validation needed.
    0 repo stars
  39. ▌
    Feature Analyzer 3 · mrciphersmith bundle
    Use when analyzing feature branch changes across repos, planning implementation, or understanding backend→frontend contracts. NEVER start without explicit user confirmation of source, target, and branch.
    0 repo stars
  40. ▌
    Gproject Planner 2 · mrciphersmith bundle
    Generates roadmap, milestones, task breakdown, and dependency graph from PRD. Use when: dispatched by gproject-orchestrator Phase 6. NOT for: direct user invocation.
    0 repo stars
  41. ▌
    Autodoc Architect 2 · mrciphersmith bundle
    Phase 3 subagent for autodoc-orchestrator. Synthesizes all module analyses into a system-level architecture description: layers, data flows, integration points, and cross-cutting concerns. Use when: dispatched by autodoc-orchestrator Phase 3. NOT for: direct user invocation.
    0 repo stars
  42. ▌
    Autodoc Assembler 2 · mrciphersmith bundle
    Phase 5 subagent for autodoc-orchestrator. Assembles all documentation sections into a cohesive package: main README.md and navigation index. Use when: dispatched by autodoc-orchestrator Phase 5. NOT for: direct user invocation.
    0 repo stars
  43. ▌
    Code Style Review 2 · mrciphersmith bundle
    Detailed code style and architecture review using code-style-patterns.mdc. Reviews current branch changes. Checks naming, organization, patterns, TypeScript usage. Use when: style validation needed, architecture review.
    0 repo stars
  44. ▌
    Dependency Update 2 · mrciphersmith bundle
    Use when checking for outdated packages or upgrading dependencies with compatibility verification.
    0 repo stars
  45. ▌
    Spec Orchestrator 2 · mrciphersmith
    Use when a user request needs to be converted into a full pre-implementation documentation suite (BRD → PRD → FSD → TRD) with iterative review at each document stage.
    0 repo stars
  46. ▌
    Review Frontend 2 · mrciphersmith bundle
    Use when a frontend review is requested, checking React component patterns, MobX state management (observer, actions, computed, reactions, lifecycle), View-Store boundaries, and TypeScript safety in changed frontend code. NOT for backend patterns, security vulnerabilities, performance bottlenecks, or cross-layer architecture.
    0 repo stars
  47. ▌
    Review Greptile 2 · mrciphersmith bundle
    Use when: a PR needs codebase-aware review using Greptile — an AI reviewer with full repository indexing. Unlike diff-only reviewers, Greptile understands cross-file impact across the entire codebase. Triggered by: "greptile review", "review with greptile", "review --greptile", or dispatched by review-orchestrator on PRs. Requires: PR number + GitHub/GitLab repo name. NOT for: path-mode reviews or diff without a PR number — use other review-* skills instead.
    0 repo stars
  48. ▌
    Test Gen 2 · mrciphersmith bundle
    Use when unit or integration tests need to be written for a specific file or module.
    0 repo stars
  49. ▌
    Gproject Discovery 2 · mrciphersmith bundle
    Collects and structures initial project information from multiple sources. Use when: dispatched by gproject-orchestrator Phase 0. NOT for: direct user invocation — always called through orchestrator.
    0 repo stars
  50. ▌
    Pr Review Comments 2 · mrciphersmith bundle
    Собирает комментарии к указанному PR (по ссылке) через GitHub MCP или gh, группирует по авторам, при комментариях от boss предлагает обновить правило core/code-review-boss-profile.mdc (с согласия пользователя), анализирует каждый комментарий и даёт объяснение и возможный фикс. Триггеры: разбери комментарии к PR, комментарии к PR, pr review comments, обнови правило по ревью boss.
    0 repo stars
  51. ▌
    Review Architecture 3 · mrciphersmith bundle
    Use when: reviewing code for architectural violations — layer violations, dependency direction mistakes, module boundary coupling, SOLID principle breaches, NestJS module/provider structure, React MVVM boundary violations, or MobX store layer misplacement. Triggered by: "review architecture", "check architecture", "architectural review", or dispatched by review-orchestrator with --architecture or --backend. NOT for: style/naming preferences, logic correctness bugs, or security vulnerabilities.
    0 repo stars
  52. ▌
    Prd Creator 3 · mrciphersmith bundle
    Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document.
    0 repo stars
  53. ▌
    Review Flow Graph 2 · mrciphersmith bundle
    Use when reviewing generic ReactFlow or graph-surface abstraction changes: public graph surface, store subclassing, layout lifecycle, internal helper boundaries, selection lifecycle, and large-graph performance. Dispatched by review-orchestrator for --flow-graph, --project-conventions, --all, or src/core/flow/** / graph abstraction changes.
    0 repo stars
  54. ▌
    Interview 2 · mrciphersmith bundle
    Use before implementation, design, or migration when requirements are unclear and targeted clarifying questions are needed to gather precise context.
    0 repo stars
  55. ▌
    Perf Check 2 · mrciphersmith bundle
    Use when measuring bundle size, detecting performance regressions, auditing slow queries, or investigating why something is slow.
    0 repo stars
  56. ▌
    Autodoc Orchestrator 2 · mrciphersmith bundle
    Autonomous reverse-engineering documentation pipeline — scans an existing codebase and produces comprehensive developer documentation without user involvement after initial setup. Use when: "autodoc", "generate docs for my project", "document this codebase", "reverse engineer documentation", "create project documentation from code", "сгенерируй документацию проекта", "задокументируй кодовую базу", "автодок", "autodoc". Trigger on: user provides a repo path, asks to document existing code, wants onboarding docs, API reference, or architecture overview generated automatically. NOT for: writing new PRDs or planning new features (use gproject-orchestrator).
    0 repo stars
  57. ▌
    Claude Md Management 2 · mrciphersmith bundle
    Use when saving session learnings, coding patterns, conventions, or commands discovered during work into CLAUDE.md files.
    0 repo stars
  58. ▌
    Gproject Spec Writer 2 · mrciphersmith bundle
    Generates PRD or Implementation Plan constrained by decisions registry, architecture doc, and best practices. Does NOT invent new architectural decisions. Use when: dispatched by gproject-orchestrator Phase 4. NOT for: direct user invocation.
    0 repo stars
  59. ▌
    Review Performance 2 · mrciphersmith bundle
    Use when a performance review is requested, checking for N+1 queries, unnecessary re-renders, memory leaks, missing indexes, large bundle imports, and synchronous blocking in changed code. NOT for security, logic correctness, style, or architecture.
    0 repo stars
  60. ▌
    Review Pr Feedback 2 · mrciphersmith bundle
    Use when: a developer has received PR review comments and wants to understand them, act on them, or extract patterns from them. Covers "analyze PR comments", "review PR feedback", "what did reviewers say", "parse PR #N", "explain PR comments", or dispatched by review-orchestrator when a PR URL is provided. NOT for: reviewing code directly — this skill reads human or bot PR feedback and makes it actionable. To review code, use the domain review skills.
    0 repo stars
  61. ▌
    Brainstorm 2 · mrciphersmith bundle
    Use when exploring architecture decisions, tech choices, feature ideas, or any open-ended problem that benefits from multiple perspectives.
    0 repo stars
  62. ▌
    Review Style 2 · mrciphersmith
    Use when: reviewing code for style, naming conventions, readability, and DRY violations — without touching logic, architecture, security, or performance. Covers "review style", "style review", "check naming", "check readability", or dispatched by review-orchestrator with --style flag. NOT for: logic bugs, architectural violations, security vulnerabilities, performance anti-patterns, or any finding that could cause a functional regression.
    0 repo stars
  63. ▌
    Gproject Orchestrator 2 · mrciphersmith bundle
    Project documentation orchestrator — builds PRDs, specs, and implementation plans through a phased pipeline of specialized subagents. Use when: "Create project documentation", "Write PRD for...", "Plan project...", "Document how to implement...", "Spec out feature...", "Project planning", "gproject", "Создай документацию проекта", "Напиши PRD". Make sure to use this skill whenever the user mentions PRD, project planning, technical specification, implementation plan, feature spec, architecture document, project documentation, or wants to plan any software project from scratch or document a new feature in an existing codebase — even if they don't explicitly say "PRD" or "spec". Also trigger on: "how should I build...", "plan out...", "what's the best approach to build...", "document the approach for...", "create a roadmap for...", "spec this out", "write requirements for...". NOT for: code implementation (use job-orchestrator), code review (use code-review skills).
    0 repo stars
  64. ▌
    Interviewer 2 · mrciphersmith bundle
    Use when requirements are ambiguous and precise clarification is needed before proceeding with a complex task.
    0 repo stars
  65. ▌
    Review Strict 2 · mrciphersmith
    Use when: a strict engineering pass is needed — either as a meta-reviewer reading consolidated findings from other reviewers and elevating weak findings, or standalone on a git diff. Covers "strict review", "review --strict", "boss review", "review as boss", or dispatched by review-orchestrator as an optional post-pass after other reviewers complete. NOT for: first-pass review (run domain reviewers first); large refactors outside the diff scope (file separately).
    0 repo stars
  66. ▌
    Code Mobx Store Review 2 · mrciphersmith bundle
    Targeted MobX store and state logic review. Checks store/actions/computed/reactions, async runInAction, state typing, View↔Store boundaries. Use when: reviewing MobX changes, state management validation.
    0 repo stars
  67. ▌
    Gproject Stack Advisor 2 · mrciphersmith bundle
    Determines project level (MVP/pet/startup/production) and recommends optimal technology stack with trade-off analysis. Use when: dispatched by gproject-orchestrator Phase 2. NOT for: direct user invocation.
    0 repo stars
  68. ▌
    Code Verifier 2 · mrciphersmith bundle
    Use when running a full quality gate after implementation — lint, type-check, tests, and import validation. Mandatory step in job-orchestrator after task-implementer and after fix iterations. Use standalone when you need a structured verification report.
    0 repo stars
  69. ▌
    Tests Creator 2 · mrciphersmith bundle
    Use when writing test cases BEFORE implementation — converts acceptance criteria into failing test stubs that task-implementer will make pass. Mandatory step in the TDD pipeline between issue-analyzer and task-implementer.
    0 repo stars
  70. ▌
    Review Security Code 2 · mrciphersmith bundle
    Use when a code-level security review is requested, checking for injection vulnerabilities, auth gaps, insecure cryptography, secrets, and OWASP Top 10 patterns in changed code. NOT for infrastructure, deployment, or dependency audits.
    0 repo stars
  71. ▌
    Review Backend 2 · mrciphersmith
    Use when: reviewing NestJS backend changes — API design, service layer, DTO validation, database patterns, and TypeScript correctness. Covers "review backend", "backend review", "review API", "review NestJS", or dispatched by review-orchestrator with --backend flag. NOT for: frontend patterns, MobX, React components, general security vulnerabilities (use review-security-code for XSS/injection/auth-bypass), or performance profiling (use review-performance).
    0 repo stars
  72. ▌
    Job Documenter 4 · mrciphersmith bundle
    Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/.
    0 repo stars
  73. ▌
    Security Audit 2 · mrciphersmith bundle
    Use when checking for dependency vulnerabilities, accidentally committed secrets, or security issues in Docker images.
    0 repo stars
  74. ▌
    Review Highload 2 · mrciphersmith
    Use when: reviewing code that will run under high concurrency or high traffic — race conditions, connection pool exhaustion, cache invalidation, missing indexes, unbounded queues, missing backpressure, retry storms, idempotency gaps, hot-path blocking I/O, and distributed systems anti-patterns. Triggered by: "review highload", "review scalability", "highload review", "review concurrency", "review --highload", or dispatched by review-orchestrator. NOT for: frontend re-render performance (review-performance), general N+1 queries (review-performance), clean code style (review-clean-code), or NestJS module structure (review-architecture).
    0 repo stars
  75. ▌
    Gproject Problem Definer 2 · mrciphersmith bundle
    Defines core problems, goals, non-goals, and success metrics from discovery data. Use when: dispatched by gproject-orchestrator Phase 1. NOT for: direct user invocation.
    0 repo stars
  76. ▌
    Review Core Boundaries 2 · mrciphersmith bundle
    Use when reviewing shared core/infrastructure module changes for dependency direction, feature-boundary leakage, abstraction stability, composition, and blast-radius risks. Dispatched by review-orchestrator for --core-boundaries, --project-conventions, --all, or src/core/** changes.
    0 repo stars
  77. ▌
    Job Orchestrator 4 · mrciphersmith bundle
    Use when a GitHub issue or complex intent needs to be analyzed, planned, and implemented end-to-end with sub-agents.
    0 repo stars
  78. ▌
    Task Implementer 3 · mrciphersmith bundle
    Use when implementing a single decomposed task from issue-analyzer end-to-end, or executing autonomous code changes from a JSON task object.
    0 repo stars
  79. ▌
    Job Documenter 2 · mrciphersmith bundle
    Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/.
    0 repo stars
  80. ▌
    Review Logic 2 · mrciphersmith
    Use when: reviewing code for logic correctness, algorithmic bugs, missing error handling, async/await mistakes, null/undefined risks, race conditions, type contract violations, or spec compliance. Dispatched by review-orchestrator for --frontend, --backend, and --all. Also invoked directly: "review logic", "check correctness", "are there any bugs here". NOT for: security vulnerabilities, performance profiling, style/naming preferences, or architectural pattern concerns — those belong in their respective specialized reviewers.
    0 repo stars
  81. ▌
    Prd Creator 2 · mrciphersmith bundle
    Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document.
    0 repo stars
  82. ▌
    Review Architecture 2 · mrciphersmith
    Use when: reviewing code for architectural violations — layer violations, dependency direction mistakes, module boundary coupling, SOLID principle breaches, NestJS module/provider structure, React MVVM boundary violations, or MobX store layer misplacement. Triggered by: "review architecture", "check architecture", "architectural review", or dispatched by review-orchestrator with --architecture or --backend. NOT for: style/naming preferences, logic correctness bugs, or security vulnerabilities.
    0 repo stars
  83. ▌
    Review Orchestrator 2 · mrciphersmith bundle
    Use when: a code review is requested and the user does not explicitly name a specialized reviewer. Handles "review", "code review", "review PR", "review --frontend", "review --backend", "review --architecture", "review --security", "review --performance", "review --style", "review --strict", "review --project-conventions", "review --legacy-profiles", "review --all". Routes to specialized reviewers in parallel and consolidates findings into one unified report. NOT for: running a single specialized reviewer — invoke it directly by name instead.
    0 repo stars
  84. ▌
    Pr Issue Documenter 2 · mrciphersmith bundle
    Use when documenting PR changes, adding a PR description, creating a linked issue for a PR, or updating an existing issue body.
    0 repo stars
  85. ▌
    Job Documenter 3 · mrciphersmith bundle
    Use when a job folder needs to be initialized, or analysis/report/review documents need to be created or updated in jobs/.
    0 repo stars
  86. ▌
    Feature Analyzer 2 · mrciphersmith bundle
    Use when analyzing feature branch changes across repos, planning implementation, or understanding backend→frontend contracts. NEVER start without explicit user confirmation of source, target, and branch.
    0 repo stars
  87. ▌
    Job Orchestrator 3 · mrciphersmith bundle
    Use when a GitHub issue or complex intent needs to be analyzed, planned, and implemented end-to-end with sub-agents.
    0 repo stars
  88. ▌
    Task Implementer 2 · mrciphersmith bundle
    Use when implementing a single decomposed task from issue-analyzer end-to-end, or executing autonomous code changes from a JSON task object.
    0 repo stars
  89. ▌
    Context Collector 2 · mrciphersmith bundle
    Use when a job needs a unified context document — gathering docs, libraries, and references for sub-agents before execution.
    0 repo stars
  90. ▌
    Pr · mrciphersmith bundle
    Use when opening a pull request for the current branch.
    0 repo stars
  91. ▌
    Iago · mrciphersmith bundle
    Use when generating or updating a Mermaid diagram for a GitHub pull request review, especially after reviewing a diff and needing to explain control flow, sequence, classes, or entity relationships. Triggered by: iago, /iago, /squawk, generate PR diagram, add Mermaid diagram to PR, or visualize this review.
    0 repo stars
  92. ▌
    Push · mrciphersmith bundle
    Use when pushing the current branch to the remote, especially when upstream tracking or safety checks are needed.
    0 repo stars
  93. ▌
    Commit · mrciphersmith bundle
    Use when committing code changes and a well-structured conventional commit message is needed, with optional amend or selective staging.
    0 repo stars
  94. ▌
    Deploy · mrciphersmith bundle
    Use when deploying to any environment (staging, production) or when a deployment pipeline needs to run.
    0 repo stars
  95. ▌
    Hookify · mrciphersmith bundle
    Use when adding automated hook behavior to Claude Code or Cursor from a natural language description.
    0 repo stars
  96. ▌
    Test Gen · mrciphersmith bundle
    Use when unit or integration tests need to be written for a specific file or module.
    0 repo stars
  97. ▌
    Changelog · mrciphersmith bundle
    Use when generating a changelog, release notes, or summarizing what changed between tags, versions, or date ranges.
    0 repo stars
  98. ▌
    Interview · mrciphersmith bundle
    Use before implementation, design, or migration when requirements are unclear and targeted clarifying questions are needed to gather precise context.
    0 repo stars
  99. ▌
    Brainstorm · mrciphersmith bundle
    Use when exploring architecture decisions, tech choices, feature ideas, or any open-ended problem that benefits from multiple perspectives.
    0 repo stars
  100. ▌
    DB Migrate · mrciphersmith bundle
    Use when creating, applying, rolling back, or checking the status of database migrations.
    0 repo stars