Real Skill packageSource verifiedClawHub registry

finishing-a-development-branch

Gunakan saat implementasi sudah selesai dan semua tes hijau, lalu perlu memutuskan cara mengintegrasikan branch (merge lokal / PR / simpan). Aktif saat user bilang 'selesaikan branch ini', 'tes lulus, mau merge?', atau 'buat PR dari branch ini'.

Identity and source

Publisher attributionSuga Nickregistry owner unverified by skillvetai
Functional categorySoftware Developmentautomatically inferred · 61% rule confidence
Package forminstruction with code4 recorded files
Canonical sourceClawHub registryclawhub:pmuhammadagus-byte:finishing-a-development-branch
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 8/24/2026.claude/skills/finishing-a-development-branch

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 8/24/2026.agents/skills/finishing-a-development-branch

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 8/24/2026skills/finishing-a-development-branch

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

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/finishing-a-development-branch
clawhub inspect @pmuhammadagus-byte/finishing-a-development-branch --version 1.0.2

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
4 / 4 inspected as text
Checked
8/24/2026, 1:20:36 PM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
1 dependency and API indicators
  • api: clawhub.ai
External clawhub result: clean

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.

Evidence checked
8/24/2026, 8:33:59 AM
Release binding
Matches this record
  • vt: clean
  • skillspector: clean
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:ca1eec56b09422147bd9a34746003b09acf422b342c7ed29326834ad491b37cd
Show up to 4 recorded paths
  • _meta.json
  • scripts/pre_merge_check.sh
  • skill-card.md
  • SKILL.md

Source changelog

finishing-a-development-branch v1.0.2 - Initial public release as version 1.0.2. - Provides a structured, step-by-step workflow for completing and integrating a development branch after implementation and all tests are green. - Details verification of tests, environment detection (repo, worktree, detached HEAD), clear option menus for integration (merge local/PR/keep), and safe cleanup procedures. - Integration decision is always left to the user; skill presents a clear menu and awaits user choice. - Includes X∞ Compliance Layer with standards for safety, reasoning, verification, and error recovery.

Release security diff

mediumCompared fixed releases 1.0.1 and 1.0.2; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.18/23/2026sha256:b2a0a58e46fd1e5988e0a46ade3c25de862921e24bd7c8670969d3e507ebb616
1.0.08/23/2026sha256:282cfc62d0659f5beb421fe1c985399459bd5e0b9ad95edd70662aaead817576