jitsusama/git-branch-convention
skills/git-branch-convention/SKILL.md
Branch naming, creation and safe transitions. Use when creating a branch, switching branches, moving commits between branches or starting new work.
$ install --global
skillsauthnpx skillsauth add jitsusama/agentic-harness.pi git-branch-conventionInstall 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: Apr 24, 2026, 8:52 PM3.3s1 file scanned
SKILL.md
- name:
- git-branch-convention
- description:
- >
Branch Management
Naming
- Format:
username/short-description - Keep total length under 40 characters
- Lowercase, hyphens between words
- Be specific:
joel/oauth-refreshnotjoel/fix
Get the username prefix via
gh api user --jq .login | tr '[:upper:]' '[:lower:]'.
Do not infer from existing branches or ask; always use
the authenticated GitHub user.
Name Conflicts
When a branch name already exists, add specificity instead of appending numbers:
oauthtaken →oauth-refresh(narrow the scope)fix-leaktaken →parser-memory-leak(add the component)api-fixtaken →api-auth-fix(add the area)
If the existing branch is doing the same work, ask whether to use it instead of creating a new one.
Before Creating
Assess the situation first:
- Is the working directory clean? Stash if dirty.
- Are there unpushed commits? They may need to move.
- What's the right base: main, a release branch, another feature branch?
- Is the current branch in a detached HEAD state?
Safe Transitions
When moving work to a new branch:
- Create the new branch from the current HEAD.
- Push the new branch.
- Return to the original branch.
- Reset the original to its remote tracking branch.
- Switch back to the new branch.
If stashed changes conflict when restoring, don't force it; flag the conflict for manual resolution.
What Not to Do
- Don't create branches from stale bases without pulling first.
- Don't leave the user on a detached HEAD.
- Don't lose commits; always verify after moving work.
- Don't force-push without discussion.
Related Skills
jitsusama/quest-format
development
VerifiedTrustedCommunity
Structure of a quest README and the documents that live under it: frontmatter shape, the four core and four optional body sections, emoji glyphs, ID format, alias notation, Cast bullets and Journey entries. Use when writing or editing a quest README, a plan, research, brief or report document under a quest. Pairs with quest-convention for choices like kind, promotion and reordering. Follow the prose-standard for voice.
5SKILL.mdUpdated Jun 4, 2026
jitsusama/quest-convention
tools
VerifiedTrustedCommunity
Operational conventions for the quest system: when to use a quest versus a subquest versus a sidequest, when to scaffold a plan or research document, how to reorder priorities, when to add optional sections, when to conclude versus retire, the resuscitate pattern. Use when driving the quest tool, deciding kind, promoting or parking work, or organising a project as quests. Pairs with quest-format for the on-disk shape.
5SKILL.mdUpdated Jun 4, 2026
jitsusama/markdown-standard
development
VerifiedTrustedCommunity
Markdown structure rules: Title Case headings with their exceptions, the line-width target and its legitimate exceptions, reference-style links, fenced code blocks with language tags, tables and lists. Use when writing or editing any markdown file (README, AGENTS, docs, plans, skill files), or when adding a heading, link, table or code block. Owns markdown structure; pairs with prose-standard, which owns voice, grammar, spelling and punctuation.
5SKILL.mdUpdated Jun 4, 2026
jitsusama/convention-recurrence-sensor-guide
tools
VerifiedTrustedCommunity
How to measure whether convention corrections keep recurring in the pi session logs, by category and by week. Use to record a baseline before the convention gates take effect and to re-run afterwards to confirm the recurring categories bend down. Pairs with the convention gates (pr-guardian, issue-guardian, commit-guardian, slack-integration) and the convention-context extension.
5SKILL.mdUpdated Jun 4, 2026