jm96441n/.config/claude/skills/bdexecissue
.config/claude/skills/bdexecissue/SKILL.md
execute a single bd issue
$ install --global
skillsauthnpx skillsauth add jm96441n/dotfiles .config/claude/skills/bdexecissueInstall 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:11 AM127.7s1 file scanned
SKILL.md
- description:
- execute a single bd issue
- argument-hint:
- <issue key>
- allowed-tools:
- Bash(bd *), Bash(tea *), Bash(jj *), Bash(ast-grep *), Bash(sg *), Read, Edit, Write, Glob, Grep
- context:
- fork
Execute Single BD Issue
Overview
Execute a single bd issue with proper status tracking, commenting, and jj workflow integration. This command handles one issue in isolation, keeping context clean.
Execute the bd issue [issue-id] following the bdexecissue workflow:
- IMMEDIATELY mark in_progress: bd update [issue-id] --status in_progress
- Review details: bd show [issue-id]
- Implement the work with atomic commits
- Track progress with bd comments after commits
- Verify acceptance criteria and tests pass
- Close when complete: bd close [issue-id] --reason "[summary]"
If blocked, create blocker issues and report back.
Report final status: completed, blocked, or needs-attention.
Arguments
$ARGUMENTS
The argument should be a bd issue ID (e.g., proj-5, app-12).
Instructions
1. Claim the Issue Immediately
bd update [issue-id] --status in_progress
⚠️ CRITICAL: Do this FIRST before any other work.
2. Review Issue Details
bd show [issue-id]
Read the description, acceptance criteria, and any existing comments carefully.
3. Implement the Work
Commit Strategy
- Commit early and often - each logical unit of working code
- Never commit broken code (except failing tests before TDD implementation)
- Clear messages - explain why, not just what
- No Claude references in commit messages
Track Progress with Comments
After each meaningful commit:
bd comment [issue-id] "Commit [hash]: [what was done]"
4. Complete the Issue
Before Closing
- ✅ All acceptance criteria met
- ✅ Tests pass (run them!)
- ✅ All changes committed to jj
- ✅ No uncommitted files related to this issue
Close with Summary
bd close [issue-id] --reason "Brief summary of what was completed"
5. Report Back
When done, provide a brief summary:
- What was implemented
- Key commits made
- Any issues discovered (should be filed with
bd create) - Final status
Handling Blockers
If you discover a blocker:
# Create blocker issue
bd create "Fix: [blocker description]" \
--priority 0 \
--description "Discovered while working on [issue-id]"
# Link dependency
bd dep add [issue-id] [blocker-id] --type blocks
# Comment on original
bd comment [issue-id] "Blocked by [blocker-id]: [reason]"
# Reopen original issue
bd update [issue-id] --status open
Then report back that the issue is blocked.
Discovering New Work
If you find additional work needed:
bd create "[New task]" \
--description "Discovered during [issue-id]: [context]"
bd comment [issue-id] "Created [new-id] for [reason]"
Continue with the original issue unless it's truly blocked.
Error Handling
If you cannot complete the issue:
- Document what was done in a comment
- Document what's blocking completion
- Either:
- Create a blocker issue and link it
- Or leave in_progress with clear comment about state
- Report back with status and blockers
Best Practices
- One Issue Focus - Don't work on other issues, stay focused
- Atomic Commits - Small, working increments
- Rich Comments - Reference commits, document decisions
- Test Before Close - Verify functionality works
- Clean Exit - Always leave issue in a valid state (closed or clearly documented)
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