📦
content-creator
88Create Brand-Consistent Marketing Content
Marketing teams need content that stays consistent across channels. This skill helps plan, write, analyze, and optimize content for brand voice and SEO.
Writing & Content View
Skills finishing-a-development-branch
📦
finishing-a-development-branch
Content revision r2 Safe ⚙️ External commands📁 Filesystem access
Finish Development Branches Safely
Completed branches often lack a clear integration and cleanup process. This skill verifies tests and guides users through merge, pull request, preservation, or discard workflows.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "finishing-a-development-branch" from https://skillstore.io/skills/sickn33-finishing-a-development-branch.md and its manifest at https://skillstore.io/api/skills/sickn33-finishing-a-development-branch/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "finishing-a-development-branch". Finish this tested feature branch.
Expected outcome:
- Tests passed.
- The branch appears to use main as its base.
- Choose local merge, pull request, keep as-is, or discard.
Using "finishing-a-development-branch". Keep the branch for later.
Expected outcome:
The branch remains unchanged, and its worktree is preserved at the current path.
Using "finishing-a-development-branch". Discard this branch.
Expected outcome:
The skill lists the branch, commits, and worktree, then waits for the exact discard confirmation before deletion.
Security Audit
Safev5 • 7/23/2026 Open versioned report
All 24 static findings are false positives. Most detections are Markdown code-fence delimiters, while the shell substitutions compose fixed text or query local Git state without reevaluating output as shell code. Standard error redirection to /dev/null is benign, and destructive cleanup requires an explicit workflow choice and typed confirmation.
1
Files scanned
212
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (23)
SKILL.md:25-28 SKILL.md:28-31 SKILL.md:31-37 SKILL.md:37-45 SKILL.md:45-48 SKILL.md:48-56 SKILL.md:56-65 SKILL.md:65-73 SKILL.md:73-88 SKILL.md:88-94 SKILL.md:94-107 SKILL.md:107-120 SKILL.md:120-127 SKILL.md:127-132 SKILL.md:132-135 SKILL.md:135-144 SKILL.md:144-146 SKILL.md:146-149 SKILL.md:149-151 SKILL.md:99-106 SKILL.md:145 SKILL.md:94-107 SKILL.md:144-146
📁 Filesystem access (1)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-finishing-a-development-branch?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-finishing-a-development-branch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-finishing-a-development-branch/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-finishing-a-development-branch.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). finishing-a-development-branch security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5BibTeX citation
@techreport{sickn33-sickn33-finishing-a-development-branch-2026,
author = {sickn33},
title = {finishing-a-development-branch security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "finishing-a-development-branch security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-finishing-a-development-branch/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-finishing-a-development-branch:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
8 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Higher Skillstore usage
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
ZhanlinCui Recommended
zhanlincui-finishing-a-development-branch
Skillstore Score 78
Evidence Confidence High
Skillstore usage 15
Updated
2026-08-21
sickn33 Current
sickn33-finishing-a-development-branch
Skillstore Score 78
Evidence Confidence High
Skillstore usage 9
Updated
2026-08-21
cygnusfear-finishing-a-development-branch
Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated
2026-08-21
davila7-finishing-a-development-branch
Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated
2026-08-21
cycleaddict-finishing-a-development-branch
Skillstore Score 78
Evidence Confidence High
Skillstore usage 6
Updated
2026-08-21
obra-finishing-a-development-branch
Skillstore Score 71
Evidence Confidence High
Skillstore usage 8
Updated
2026-08-21
dyai2025-finishing-a-development-branch
Skillstore Score 69
Evidence Confidence High
Skillstore usage 8
Updated
2026-08-21
codingcossack-finishing-a-development-branch
Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 7
Updated
2026-08-21
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Complete a Feature Branch
Verify a completed feature, choose an integration path, and clean local resources when appropriate.
Prepare a Reviewed Pull Request
Push tested work and create a pull request with a concise summary and test plan.
Close Automated Development Work
Give an AI coding workflow explicit approval points before merging, preserving, or deleting work.
Try These Prompts
Finish My Branch
Finish my current development branch. Verify tests first, identify the base branch, then present the available completion options.
Create a Pull Request
Verify this branch, push it, and create a pull request with a summary and test plan. Ask before any cleanup.
Merge Locally
Confirm the base branch, run tests, merge this feature locally, and test the merged result. Remove the feature branch only after success.
Audit and Complete Branch Work
Inspect branch and worktree state, verify tests, and present all four completion choices. Require exact confirmation before deleting any branch or worktree.
Best Practices
- Start with a clean worktree and a known base branch.
- Run tests before choosing a workflow and after a local merge.
- Review branch names, commits, and paths before confirming cleanup.
Avoid
- Do not continue when the test suite fails.
- Do not delete a branch or worktree without exact user confirmation.
- Do not force-push or change remote history without an explicit request.
Frequently Asked Questions
When should I use this skill?
Use it after implementation is complete and you need to integrate, preserve, or discard a tested branch.
What happens when tests fail?
The workflow stops, reports the failures, and does not offer merge or pull request actions.
Can it create a pull request?
Yes. It can push the branch and use GitHub CLI to create a pull request with a test plan.
Does it delete work automatically?
No. Discarding work requires the user to type an exact confirmation before branch or worktree deletion.
Does it support Git worktrees?
Yes. It preserves or removes a worktree according to the selected completion option.
Can it resolve merge conflicts?
No. Conflict resolution remains a separate task that requires repository-specific review and testing.
Developer Details
Author
sickn33License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
7 downloads · 114 views
File structure
📄 SKILL.md
More from sickn33
View all📦
prompt-engineering-patterns
85Improve LLM Prompts With Proven Patterns
Inconsistent prompts waste time and make AI outputs hard to trust. This skill guides prompt design with reusable patterns, examples, evaluation steps, and optimization workflows.
Productivity View
📦
senior-fullstack
82Build Fullstack Apps with Senior Patterns
Teams need consistent setup, architecture, and review guidance for modern web applications. This skill provides scaffolders, workflow references, and quality prompts for React, Next.js, Node.js, GraphQL, and PostgreSQL projects.
Coding & Development View
📦
senior-architect
81Design Scalable Software Architectures
Architecture decisions are hard to compare across web, mobile, backend, and cloud systems. This skill provides structured guides and local scaffold scripts for reports, dependency review, and trade-off documentation.
Coding & Development View
📦
prompt-engineer
81Optimize AI Prompts With Prompt Engineer
Writing clear prompts is hard when goals are vague or complex. This skill turns rough requests into structured prompts using proven prompt frameworks.
Productivity View
📦
product-manager-toolkit
80Prioritize Product Work With Research Insights
Product teams need faster ways to rank features, synthesize interviews, and document decisions. This skill provides RICE scoring, interview analysis, and PRD templates for structured planning.
Productivity View
Related Skills
View all📦
git-advanced
86Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Coding & Development View
📦
testing
85Build Reliable Test Automation
by 89jobrien
Weak tests slow releases and hide regressions. This skill guides test strategy, TDD, automation, coverage review, and Playwright web checks.
Coding & Development View
📦
code-reviewer
83Review Code with Structured Quality Checks
by alirezarezvani
Code reviews can miss quality, security, and maintainability issues. This skill guides structured reviews with scripts, checklists, and report generation.
Coding & Development View
📦
testing-patterns
81Plan Reliable Tests Across Your Codebase
by 0xDarkMatter
This skill helps teams choose test strategies, mocks, data fixtures, coverage gates, and CI patterns without mixing test scopes. It gives Claude, Codex, and Claude Code structured guidance for unit, integration, end-to-end, TDD, and pipeline testing.
Coding & Development View
📦
systematic-debugging
81Debug Technical Failures Systematically
by Asmayaseen
Quick fixes often hide the real cause and create regressions. This skill structures investigation, hypothesis testing, implementation, and verification around collected evidence.
Coding & Development View
📦
golang-testing
81Build Better Go Tests
by 89jobrien
Go teams need consistent tests across units, integrations, mocks, benchmarks, and coverage. This skill provides practical Go testing patterns that Claude, Codex, and Claude Code can apply during development.
Coding & Development View