jm96441n/session-close
.config/claude/skills/session-close/SKILL.md
Protocol for properly ending a coding session - ensures all work is committed, pushed, and handed off correctly.
$ install --global
skillsauthnpx skillsauth add jm96441n/dotfiles session-closeInstall 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 6, 2026, 9:14 AM144.8s1 file scanned
SKILL.md
- name:
- session-close
- description:
- Protocol for properly ending a coding session - ensures all work is committed, pushed, and handed off correctly.
- license:
- MIT
- compatibility:
- opencode
- category:
- workflow
- tools:
- jj, bd
When to use me
Use this skill when ending a work session. This ensures all work is properly saved, pushed, and documented for the next session.
Landing the Plane (Session Completion)
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until jj git push succeeds.
MANDATORY WORKFLOW:
- File issues for remaining work - Create issues for anything that needs follow-up
- Run quality gates (if code changed) - Tests, linters, builds
- Update issue status - Close finished work, update in-progress items
- PUSH TO REMOTE - This is MANDATORY:
jj git fetch jj rebase -d main bd sync jj bookmark set <bookmark-name> jj git push -b <bookmark-name> jj status # Verify push succeeded - Clean up - Clear stashes, prune remote branches
- Verify - All changes committed AND pushed
- Hand off - Provide context for next session
Critical Rules
- Work is NOT complete until
jj git pushsucceeds - NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds
Checklist
Before saying "done" or "complete", run this checklist:
[ ] 1. jj status (check what changed)
[ ] 2. jj describe -m "..." (describe current commit)
[ ] 3. bd sync (sync beads changes)
[ ] 4. jj bookmark set <name> (set bookmark on current commit)
[ ] 5. jj git push -b <name> (push to remote)
NEVER skip this. Work is not done until pushed.
Related Skills
jm96441n/session-close
tools
VerifiedTrustedCommunity
Protocol for properly ending a coding session - ensures all work is committed, pushed, and handed off correctly.
39SKILL.mdUpdated Apr 6, 2026
jm96441n/jujutsu
tools
VerifiedTrustedCommunity
Prefer Jujutsu (jj) over git for version control. Use squash workflow pattern where commits are described first, then changes are made in a scratch child commit and squashed into the parent.
39SKILL.mdUpdated Apr 6, 2026
jm96441n/.config/opencode/skill/jira
development
VerifiedTrustedCommunity
# Jira Skill Guidelines for creating and managing Jira issues for HashiCorp projects. ## InfraGraph Project (IG) ### Project Information - **Project Key**: `IG` - **Team Field**: `customfield_10001` - **Default Team Value**: `"InfraGraph-Graph Engine"` ### Creating Issues When creating Jira issues for the InfraGraph project, always include the team field: ```python jira_create_issue( project_key="IG", summary="Task summary", issue_type="Task", description="Task description
39SKILL.mdUpdated Apr 6, 2026
jm96441n/gremlin
development
VerifiedTrustedCommunity
Write Gremlin graph traversal queries for Neptune using the gremlin-go driver patterns in this codebase
39SKILL.mdUpdated Apr 6, 2026