ramblurr/finishing-a-development-branch
prompts/skills/finishing-a-development-branch/SKILL.md
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
development
Updated May 21, 2026
$ install --global
skillsauthnpx skillsauth add ramblurr/nix-devenv finishing-a-development-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 5:43 AM125.2s1 file scanned
SKILL.md
- name:
- finishing-a-development-branch
- description:
- Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
<required>
**CRITICAL: Follow these steps in order:**
- Run the project's local qa/test suite
# Run project's qa suite
bb qa / bb test / npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before creating PR:
[Show failures]
Cannot proceed until tests pass.
-
Confirm that there is some formatting/lint/typechecking in the project. If NONE of these exist, ask me if there was something that you missed.
-
Run any formatters and fix issues in a subagent.
-
Use the Skill(code-reviewer) to do a self review. You do NOT have to follow the subagent's suggestions. This is merely a way to get a fresh pair of eyes on the code.
-
Confirm that you are not on the main branch. If you are, ask me before proceeding. NEVER push to main without permission.
-
Use
git addto stage the changes to files you edited for this feature. FollowCommit message rules:
- Never mention beads, bd issues in the commit message
- Never use bold formatting
- Never use emoji in the commit message
- Never mention Claude/AI/LLMS/Coding Agents in the commit message
- Do not list or mention files in the commit message (that is redundant, the commit itself has a list of files)
- Do not include other redundant or obvious information
- Use
git log -n 10to look at past 10 commits, follow a similar commit message style (number of lines, casing etc)
-
[OPTIONAL] Push and create a PR.
Only push and create a PR if the human operator told you to, otherwise stop with the commit.
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets of what changed>
## Test Plan
- [ ] <verification steps>
EOF
)"
- Make sure the PR branch CI succeeds. Skip if there are no checks/ci.
# Check if the PR CI succeeded
gh pr checks
# If it is still running, sleep and check again
sleep 60 && gh pr checks
If CI did not pass, examine why. If the CI did not start, this is likely due to merge conflicts; merge main, fix conflicts, and try again. <system-reminder>Do not move forward without a ci status unless you have checked for merge conflicts</system-reminder>
- Make changes as needed, push a new commit, and repeat the process. <system-reminder> It is critical that you fix any ci issues, EVEN IF YOU DID NOT CAUSE THEM. </system-reminder>
- Tell me: "I can automatically get review comments, just let me know when to do so." </required>
Related Skills
ramblurr/nixbot
tools
VerifiedTrustedCommunity
Use when working with Nixbot CI, forge commit statuses, Nix flake checks, nixbot.toml, Nixbot effects, or nixbot-cli - explains how Nixbot runs flake CI and how to inspect builds and logs.
SKILL.mdUpdated Jun 12, 2026
ramblurr/operational-change-protocol
testing
VerifiedTrustedCommunity
Use this OCP when executing or preparing to execute commands that change a live or important system, service reloads/restarts, package changes, deployments, migrations, firewall/network/access changes, credential rotation, NixOS switch/test/boot/deploy, or incident mitigation. It guides safe operations with a persisted ledger for scope, preflight, baseline, rollback, validation, and evidence.
SKILL.mdUpdated Jun 4, 2026
ramblurr/write-a-skill
development
VerifiedTrustedCommunity
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
SKILL.mdUpdated May 21, 2026
ramblurr/prompts-documents
documentation
VerifiedTrustedCommunity
Naming conventions for workflow documents in prompts/. Use when creating plans, PRDs, research reports, idea capture or other workflow documents. Triggers on (1) creating new planning documents, (2) naming PRDs or research reports, (3) questions about document organization in prompts/.
SKILL.mdUpdated May 21, 2026