Menu

Individual skill

sem

Use sem for entity-level (function/class/method) code questions in any Git repo. Four questions, four verbs - where is it (sem find, sem grep), what does my change touch (sem impact), is it correct (sem check), what should a human review (sem certify). Trigger whenever the user asks where something is defined or called, what a change breaks or which tests to run, whether a change is correct, what changed in a commit or PR, or what to review; also use it proactively before refactors and in code review, where line-level git output is noisy.

agent-skill/SKILL.md

Read pinned source

Source commit e527a5aa95a14260d8a30d7c45d84e66158cef6f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,443
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# sem

sem parses 30+ languages with tree-sitter and answers questions about entities
(functions, classes, methods) and the calls between them. Instead of "lines
43-51 changed" it says "function `validateToken` in `src/auth.ts` was
modified, and these 3 callers and 2 tests reach it". It works in any Git repo
with no setup. Answers are deterministic; when a caller set may be incomplete,
sem says so.

## Four questions, four verbs

| Question | CLI | MCP tool |
|---|---|---|
| Where is it? | `sem find NAME`, `sem grep TEXT` | `sem_find`, `sem_grep` |