vibesubin

Coordinate nine code-hygiene specialists to produce a prioritized repo report.

50|2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/subinium/vibesubin --skill vibesubin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibesubin
Source: https://github.com/subinium/vibesubin/tree/main/plugins/vibesubin/skills/vibesubin
Command: npx skills add https://github.com/subinium/vibesubin --skill vibesubin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate and synthesize nine code-hygiene specialists in parallel to produce a single, prioritized repo report that surfaces issues, routes work to the right sub-skills, and keeps edits read-only until the operator approves fixes.

Core Features & Use Cases

  • Parallel sweeps across multiple specialists to achieve broad, fast coverage.
  • Routing: map vague requests to the appropriate sub-skills or direct-call workflows like audit-security or refactor-verify.
  • Safety and clarity: read-only sweep output with the option to enable harsh mode and layperson explanations, surfacing skill conflicts when needed.

Quick Start

Type /vibesubin to run a full parallel sweep across code-hygiene specialists and review the prioritized report.

Frequently Asked Questions about vibesubin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run all code-hygiene checks across my repository in one sweep?

You can run all code-hygiene checks in one sweep by triggering a parallel sweep command that coordinates nine specialists to synthesize a single prioritized repo report.

What is the best way to audit a codebase for multiple hygiene issues at once?

Auditing a codebase for multiple hygiene issues at once is best handled by a parallel sweep across code-hygiene specialists, producing a single prioritized report that surfaces conflicts when specialists disagree.

How does code-hygiene routing work for vague code audit requests?

Code-hygiene routing maps vague audit requests to the appropriate sub-skills or direct-call workflows, ensuring the correct analysis is performed without manual intervention.

Can I review code audit findings before any files are modified?

Yes, code audit sweeps run in read-only mode and only modify files when the operator explicitly approves the fixes surfaced in the final prioritized report.

Does the parallel sweep support harsh mode and layperson explanations for repo audits?

Yes, parallel repo audits support harsh mode for stricter findings and layperson explanations for accessibility, while also surfacing any conflicts when specialists disagree.

How do I use direct-call workflows for specific code checks like security audits?

You can use direct-call workflows to route vague requests to specific code checks like audit-security or refactor-verify, bypassing the full parallel sweep when a targeted analysis is needed.