MLOps.community avatar

MLOps.community

Official

@mlopscommunity · Worldwide

0Followers
|
14Public Repos
|
16Published Skills

Facilitates distributed engineering coordination through adversarial code review, visual regression testing, and structured context window management for complex repository environments.

Skills Distribution
DomainDeveloper To...Quality Assurance .. (35%)Repository Governa.. (35%)Contextual Planning (30%)

Agent Skills by MLOps.community

Showing 16 vetted skills indexed across 1 GitHub repositories.

mlopscommunitymlopscommunity
37

expert-persona-skills

Activate latent domain expertise in Claude for non-coding specializations.

Official
Intermediate
mlopscommunitymlopscommunity
37

validation-runner

Executes linting, unit, UI validation, E2E tests, and log analysis in an isolated environment.

Official
Advanced
mlopscommunitymlopscommunity
37

adversarial-code-review

Run three-agent adversarial code reviews on pull requests with confidence scoring.

Official
Advanced
mlopscommunitymlopscommunity
37

hooks-and-enforcement

Configure Claude Code lifecycle hooks to enforce quality and security checks via settings.json.

Official
Advanced
mlopscommunitymlopscommunity
37

merge-conflict-resolution

Resolve syntactic and semantic merge conflicts from parallel agent work.

Official
Advanced
mlopscommunitymlopscommunity
37

product-research

Synthesize raw research data into product insights for competitive analysis.

Official
Advanced
mlopscommunitymlopscommunity
37

brainstorming-planner

Probe project goals, scope, dependencies, and acceptance criteria into phased plans.

Official
Intermediate
mlopscommunitymlopscommunity
37

agent-maintained-docs

Embed file header descriptions and folder READMEs enforced by git hooks.

Official
Intermediate
mlopscommunitymlopscommunity
37

objective-research

Separate agent contexts to research code paths and data flow objectively.

Official
Intermediate
mlopscommunitymlopscommunity
37

visual-regression

Capture UI screenshots with Playwright and compare visual differences between code versions.

Official
Advanced
mlopscommunitymlopscommunity
37

documentation-first-setup

Generates project documentation for agents covering code architecture and workflows.

Official
Intermediate
mlopscommunitymlopscommunity
37

context-window-management

Manage AI context window utilization by budgeting instructions, offloading results, and saving session state.

Official
Intermediate
mlopscommunitymlopscommunity
37

parallel-agent-management

Execute multiple AI agents in parallel using Git worktrees and communication contracts.

Official
Advanced
mlopscommunitymlopscommunity
37

three-layer-memory

Configure tiered persistent memory across global, repository, and external markdown sources.

Official
Advanced
mlopscommunitymlopscommunity
37

crispi-planning

Separate research, design, and implementation into distinct context windows.

Official
Advanced
mlopscommunitymlopscommunity
37

voice-first-planning

Convert spoken transcripts into structured feature specifications and requirements.

Official
Basic

Frequently Asked Questions About MLOps.community

FAQPage Schema
What specific engineering tasks are enabled by these capabilities?

These capabilities enable automated linting, unit testing, and end-to-end validation within isolated environments. Users can perform semantic merge conflict resolution, enforce documentation standards via git hooks, and synthesize raw research data into structured product requirements using voice-to-specification conversion.

Which technical personas benefit most from these repository management skills?

Senior software engineers, technical leads, and quality assurance architects benefit most. These skills are designed for teams managing high-velocity codebases who require rigorous adversarial review, parallelized development cycles, and strict adherence to documentation and security standards within their version control systems.

What are the primary prerequisites for implementing these quality and review standards?

Implementation requires a git-based repository structure and the configuration of settings.json to manage lifecycle hooks. Users must also establish tiered persistent memory sources, such as markdown files or global repositories, to support the context window management and parallel agent coordination features.