代码评审

cross-eval

youlianvr

"/cs:cross-eval <memo> — Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation. Use when a high-stakes memo needs an independent sanity check before the boardroom — e.g. a bet-the-company pivot or fundraise terms."

brainstorming

youlianvr

"You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Adapted 2026-08-09 for this workspace: design docs go to knowledge/findings/, handoff goes to executing-plans (not writing-plans)."

gitnexus-impact-analysis

abhigyanpatwari

Analyze blast radius before making code changes

pr-writing-review

evalstate

Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer suggestions to help refine future writing.

Regression Verification Audit

matiaszanolli

"Verify closed bug fixes haven't regressed — dynamically discovers and checks"

problem-analysis

solatis

Invoke IMMEDIATELY via python script when user requests problem analysis or root cause investigation. Do NOT explore first - the script orchestrates the investigation.

telnyx-account-go

team-telnyx

Manage account balance, payments, invoices, webhooks, and view audit logs and detail records. This skill provides Go SDK examples.

gitnexus-impact-analysis

abhigyanpatwari

"Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\""

ln-003-push-all

levnikolaevich

"Commit and push ALL changes (staged + unstaged + untracked) to the remote repository"

ln-512-tech-debt-cleaner

levnikolaevich

"Automated tech debt cleanup worker (L3). Reads codebase audit findings, applies safe auto-fixes for low-risk issues (unused imports, dead code, commented-out code, deprecated aliases). Confidence >=90% only. Creates single commit with summary."

ln-620-codebase-auditor

levnikolaevich

"Coordinates 9 specialized audit workers (security, build, architecture, code quality, dependencies, dead code, observability, concurrency, lifecycle). Researches best practices, delegates parallel audits, aggregates results into docs/project/codebase_audit.md."

ln-311-agent-reviewer

levnikolaevich

"Worker that runs parallel external agent reviews (Codex + Gemini) on Story/Tasks. Background tasks, process-as-arrive, critical verification with debate. Returns filtered suggestions for Story validation."

ln-403-task-rework

levnikolaevich

Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task.

ln-100-documents-pipeline

levnikolaevich

"Top orchestrator for complete doc system. Delegates to ln-110 coordinator (project docs via 5 L3 workers) + ln-120-150 workers. Phase 4: global cleanup. Idempotent."

ln-400-story-executor

levnikolaevich

"Orchestrates Story tasks. Prioritizes To Review -> To Rework -> Todo, delegates to ln-401/ln-402/ln-403/ln-404. Sets Story to To Review when all tasks Done (NOT Done — quality gate handles that). Metadata-only loading up front."

detect-project

RHEcosystemAppEng

Analyze a project folder or GitHub repository to detect programming language, framework, and version requirements. Use this skill when containerizing an application, selecting an S2I builder image, deploying to OpenShift or RHEL, or determining a project's tech stack. Supports Node.js, Python, Java, Go, Ruby, .NET, PHP, and Perl. Triggers on /detect-project command or when user needs build strategy recommendations. Run before /s2i-build or /rhel-deploy.

find-skills

mastra-ai

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

playbook-generator

RHEcosystemAppEng

CRITICAL: This skill must be used for playbook generation. DO NOT use raw MCP tools like create_vulnerability_playbook directly. Generate production-ready Ansible remediation playbooks for CVE vulnerabilities with Red Hat best practices, error handling, and Kubernetes safety patterns. Use this skill when you need to create remediation playbooks that follow Red Hat Lightspeed patterns and incorporate RHEL-specific considerations. This skill orchestrates MCP tools (create_vulnerability_playbook) while consulting documentation (cve-remediation-templates.md, package-management.md) to enhance playbooks with Red Hat best practices and RHEL-specific patterns. IMPORTANT: ALWAYS use this skill instead of calling create_vulnerability_playbook directly for playbook generation.

existing-repo

alinaqi

Analyze existing repositories, maintain structure, setup guardrails and best practices

base

alinaqi

Universal coding patterns, constraints, TDD workflow, atomic todos

codex-review

alinaqi

OpenAI Codex CLI code review with GPT-5.2-Codex, CI/CD integration

agent-teams

alinaqi

Claude Code Agent Teams - default team-based development with strict TDD pipeline enforcement

deep-analysis

cyberkaida

Performs focused, depth-first investigation of specific reverse engineering questions through iterative analysis and database improvement. Answers questions like "What does this function do?", "Does this use crypto?", "What's the C2 address?", "Fix types in this function". Makes incremental improvements (renaming, retyping, commenting) to aid understanding. Returns evidence-based answers with new investigation threads. Use after binary-triage for investigating specific suspicious areas or when user asks focused questions about binary behavior.

3D Modeling

omer-metin