Skills/ClawHub/mobile-merge-request

mobile-merge-request@1.0.1

CAUTION

Publisher claims: "Guides the merge request and pull request workflow for mobile teams: branch naming, Conventional Commits, small and stacked MRs, self-review, rebase vs merge, safe conflict resolution for lockfiles, project.pbxproj and version catalogs, MR descriptions with screenshots and rollback, and reviewer etiquette. Use when creating branches, writing commits or MR descriptions, rebasing, resolving conflicts or answering review comments." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher ahmadhussain0335 · joined 7 days agoInstalls 103Last detonated 26 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-02 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

No findings across 817 lines in 5 files.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim ahmadhussain0335: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim ahmadhussain0335