changelog: Enhanced with ClawHub metadata, expanded examples, and rationalization prevention
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/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/<skill-name>SKILL.mdRuntime, 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 @pmuhammadagus-byte/receiving-code-reviewclawhub inspect @pmuhammadagus-byte/receiving-code-review --version 1.0.2This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
Unexpected flow-seq-start at node end at line 2, column 52: description: "Gunakan skill ini saat: code-review" [shape=box];; > "Before impl… ^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:e2361d2293a8edfcf3890f299010bf6d6bac2c0fc13d4c40489711e59bc123e4_meta.jsonscripts/__pycache__/classify_comments.cpython-314.pycscripts/classify_comments.pyskill-card.mdSKILL.md- Improved description clarity; fixed frontmatter description to match actual skill purpose and triggers. - Added explicit purpose, metadata, and structured compliance nodes in line with Skill Architecture Standard X∞. - Documented when and how to trigger the skill, including negative triggers. - Clarified required response pattern for code review: verify before implementing, avoid performative agreement, and focus on technical correctness. - Provided detailed instructions for handling unclear or conflicting feedback and outlined pushback scenarios. - Included guidelines for acknowledgment, implementation order, and handling external or "professional" feature requests.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
Permission escalation detectedThese older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:a99a908c314db10a72ab0a5119db2284ba8d848639a6ee53221643122d6676ecsha256:252861816d493ede3ff817d3ca0b9d2ce26f507ac0e437701e9de78239dc4f01