knoopx/sem
agent/skills/sem/SKILL.md
Semantic version control analysis. Use sem to understand actual code changes vs cosmetic/stylistic modifications, identify impacted entities, and review diffs at the semantic level.
$ install --global
skillsauthnpx skillsauth add knoopx/pi semInstall 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 5, 2026, 8:16 AM125.4s1 file scanned
SKILL.md
- name:
- sem
- description:
- Semantic version control analysis. Use sem to understand actual code changes vs cosmetic/stylistic modifications, identify impacted entities, and review diffs at the semantic level.
sem (Semantic Version Control)
Analyzes code changes at the semantic level — distinguishes meaningful behavioral modifications from cosmetic or stylistic changes.
Key Commands
sem diff HEAD~1 # Show semantic diff of last commit
sem diff --commit <hash> # Show changes in a specific git commit
sem impact parseDate # See what depends on a changed function
sem impact parseDate --tests # See tests affected by entity changes
Understanding Output
Changes are marked with symbols:
~cosmetic — formatting, whitespace, style updates →style:orformat:commit type∆modified — actual behavioral change →feat:,fix:,refactor:+added — new function, class, or type →feat:-removed — deleted entity →refactor:,chore:
Typical Workflow with Jujutsu
When working with jj, convert change IDs to git commit hashes first:
# Step 1: Get the git commit hash for a jj change ID
jj log -r <change-id> -T 'commit_id' --no-graph
# Example: jj log -r nlukrrtnmlnz -T 'commit_id' --no-graph
# Output: 45a1bf3ef4cb1c68828a08558583281f9c539751
# Step 2: Use that hash with sem
sem diff --commit 45a1bf3ef4cb1c68828a08558583281f9c539751
# Step 3: Verify you have the right commit
jj show <change-id>
jj diff --name-only -r <change-id>
# Step 4: Write accurate commit description based on semantic changes
jj desc -r <change-id> -m "<type>(<scope>): <description>"
When to Use sem
Before describing commits: Run sem diff HEAD~1 to see the true scope of changes. If all changes are ~ (cosmetic), use style: or format:. If ∆ exists, describe the actual behavior change.
Large diffs with few semantic changes: A diff may touch 80 files but sem might show only 3 functions modified — most changes are stylistic. Focus your commit description on that.
Tips
- Always use
sembefore writing commit messages — it reveals the true scope - Convert jj revisions to git hashes with
jj log -r <change-id> -T 'commit_id' --no-graph - Use
sem impactto understand downstream effects before making changes - Large file counts don't always mean large semantic changes
Related Skills
- jujutsu: Version control with jj
- conventional-commits: Commit message format based on sem analysis
Related Skills
knoopx/notify
tools
VerifiedTrustedCommunity
Inform the user what is happening — skip passive lookups
52SKILL.mdUpdated May 20, 2026
knoopx/markdown-rendering
development
VerifiedTrustedCommunity
Renders markdown to self-contained HTML with a custom dark stylesheet and opens in browser. Use when previewing markdown documents, generating styled HTML from README or report files.
52SKILL.mdUpdated May 20, 2026
knoopx/jj-hunk
testing
VerifiedTrustedCommunity
Programmatic hunk selection for Jujutsu — split, commit, or squash specific hunks without interactive prompts. Use when making partial commits or selective squashes.
52SKILL.mdUpdated May 18, 2026
knoopx/jj-core
content-media
VerifiedTrustedCommunity
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
52SKILL.mdUpdated May 18, 2026