.claude/skills/vibegitRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Estimate how much of a git repository is AI-assisted and how sloppy it is. Use when the user asks whether a repo (or recent work) is "vibe coded", wants an AI-slop score, a repo health/quality snapshot, a badge, or a CI gate based on commit history. Read-only - commit metadata only, no file contents, no network.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/vibegitRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/vibegitRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/vibegitRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @thiennhant95/vibegitclawhub inspect @thiennhant95/vibegit --version 1.0.3This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:b5309be5695c4c0c1d84f3fe81413436d3b2552dd725e1f201d7f2b9b6a6f43cEVIDENCE_test_run.txtexamples/github-action.ymlLICENSEREADME.mdREADME.vi.mdskill-card.mdSKILL.mdvibegit.pyDocs: ClawHub install command and related skills (vibecheck, skill-firewall, undo-first). No code changes; 11 tests.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:b9d2cd2f30d0ebb80f7a7ddb0207495a22c4c6155099acbe858307a41f2f3f05