Smell Check
Zhen-Bo/smell-check
Runs a smell-first audit on a user-chosen path set: measures structure metrics, applies a named size profile, and reports code smells and test smells with evidence strength.
Keep all scoped code work contained to the user-defined changeset.
Install Changeset Scope
$ npx skills add timmo001/system-bridge --skill changeset-scope -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install timmo001/system-bridge changeset-scope --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/changeset-scope .claude/skills/changeset-scope && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "changeset-scope" agent skill from https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scope into .claude/skills/changeset-scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-scope", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scopeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add timmo001/system-bridge --skill changeset-scope -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install timmo001/system-bridge changeset-scope --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/changeset-scope .agents/skills/changeset-scope && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "changeset-scope" agent skill from https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scope into .agents/skills/changeset-scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-scope", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add timmo001/system-bridge --skill changeset-scope -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install timmo001/system-bridge changeset-scope --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/changeset-scope .cursor/skills/changeset-scope && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "changeset-scope" agent skill from https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scope into .cursor/skills/changeset-scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-scope", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/timmo001/system-bridge.git --path .agents/skills/changeset-scope--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add timmo001/system-bridge --skill changeset-scope -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install timmo001/system-bridge changeset-scope --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/changeset-scope .gemini/skills/changeset-scope && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "changeset-scope" agent skill from https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scope into .gemini/skills/changeset-scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-scope", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install timmo001/system-bridge changeset-scopeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add timmo001/system-bridge --skill changeset-scope -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/changeset-scope .github/skills/changeset-scope && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "changeset-scope" agent skill from https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scope into .github/skills/changeset-scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-scope", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add timmo001/system-bridge --skill changeset-scope -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install timmo001/system-bridge changeset-scope --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/timmo001/system-bridge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/changeset-scope .opencode/skills/changeset-scope && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "changeset-scope" agent skill from https://github.com/timmo001/system-bridge/tree/dev/.agents/skills/changeset-scope into .opencode/skills/changeset-scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-scope", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
changeset-scope- GitHub stars
- 356
- Token cost
- ~1.2k tokens
- SKILL.md length
- 659 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Keep all scoped code work contained to the user-defined changeset.
- Works in 4 steps: Explicit user instructions about files,… → The review, diff, pull request, injected… → Current branch changes against their… → …
- Review when explicit instructions
- SKILL.md covers Resolve The Boundary, Context Is Not Scope, Reviews and Implementation And Refactoring, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Changeset Scope is an agent skill from timmo001/system-bridge. Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests and Refactoring. The repository describes itself as: A bridge for your systems. The licence is Apache-2.0.
When your agent uses it
- Review when explicit instructions
- Injected work scopes define the boundary
Example prompts
- “/changeset-scope”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Explicit user instructions about files, behaviour, concerns, or amount of change.
- The review, diff, pull request, injected work scope, or named changeset supplied by the current workflow.
- Current branch changes against their base when the task concerns that branch.
- For standalone implementation only, the files and callers required to complete the requested behaviour.
What it can do on your machine
Read from SKILL.md and the folder at commit 608d62d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Changeset Scope loads about 1.2k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 659 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from timmo001/system-bridge at commit 608d62d, republished under its Apache-2.0 licence (© timmo001). 659 words, ~1,184 tokens.
Download SKILL.mdSave it as
.claude/skills/changeset-scope/SKILL.md (or your agent's skills folder).- name
- changeset-scope
- description
- Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.
- license
- Apache-2.0
Changeset Scope
This skill owns containment, not scope discovery. Use the scope supplied by the user, command, agent, or context provider. When branch-context-consumer is active, it remains authoritative for parsing the injected scope.
Apply this contract before investigation, delegation, domain skills, or execution so later work cannot silently widen the boundary.
Resolve The Boundary
Use the first applicable source:
- Explicit user instructions about files, behaviour, concerns, or amount of change.
- The review, diff, pull request, injected work scope, or named changeset supplied by the current workflow.
- Current branch changes against their base when the task concerns that branch.
- For standalone implementation only, the files and callers required to complete the requested behaviour.
A narrower user instruction always narrows a broader supplied changeset. Do not widen an explicit scope without asking.
The boundary is a hard limit, not a starting point for discovery. Similarity, proximity, shared ownership, or an opportunity for consistency does not bring code into scope.
Context Is Not Scope
- Read unchanged files, callers, tests, history, and documentation when needed to understand changed behaviour.
- Do not turn issues found in that surrounding context into independent findings or edits.
- Follow outside the initial files only when the changeset alters their behaviour or they provide evidence that a changed path is incorrect.
- Use surrounding code to detect a conflict with an existing contract or an existing implementation the changed code should reuse. Report it only when the changed code creates the conflict or concrete duplication; anchor the finding to the changed line, not the unchanged context.
- Treat unrelated pre-existing problems as out of scope. Mention one only as a residual risk when it directly limits confidence in the scoped work.
Reviews
- Every finding must identify a problem introduced or worsened by the changeset. A pre-existing problem, even in a touched file, is not a finding unless the changeset makes its impact worse.
- Anchor each finding to a changed line and explain the concrete path from that line to the failure. If that trace cannot be made, omit the finding.
- Apply every companion skill as criteria within this same boundary. Loading a type, framework, cleanup, security, or engineering-principles skill never expands finding scope.
- Do not recommend unrelated cleanup, migration, redesign, or consistency work as review findings.
- Do not inventory all violations of a loaded skill. Evaluate only changed code and changed behaviour against it.
- Do not expand review scope to make a suggested fix more complete. Give the smallest fix direction that resolves the scoped problem.
- Do not add praise, optional improvements, or nice-to-haves to fill out an otherwise empty review.
- Reviews remain read-only unless the user separately asks for implementation.
Show full SKILL.md (216 more words)Show less
Implementation And Refactoring
- Edit only what the requested behaviour requires.
- Change callers outside the initial files only to preserve or complete the scoped contract; stop propagation at the first stable boundary.
- Do not use a scoped task to standardise nearby code or adopt a pattern across the subsystem.
- Do not add adjacent cleanup because a file is already being edited.
- If correctness requires materially broader work, explain why and ask before widening scope.
Diagnosis And Investigation
- Investigate the scoped symptom or changed behaviour, not the health of the surrounding subsystem.
- Trace dependencies and callers as evidence, but do not convert newly observed adjacent problems into work items.
- Instrument or reproduce only as broadly as needed to distinguish causes of the scoped problem.
- A root cause outside the initial files may enter scope only when evidence shows it causes the requested failure; stop once that causal path is corrected.
Delegation
- Give delegated agents the same explicit boundary and state that surrounding reads are context only.
- Treat subagent suggestions outside the boundary as out of scope, regardless of their severity or usefulness.
- Do not let parallel exploration combine into a broader aggregate task than the user requested.
Reporting
State the scope source used. If no scoped finding or safe edit exists, say so rather than substituting adjacent work.
© timmo001, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/changeset-scope of timmo001/system-bridge.
Open the folder on GitHubat commit 608d62d
Compare with similar skills
Changeset Scope next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Changeset Scope this skilltimmo001/system-bridge | 356 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Smell CheckZhen-Bo/smell-check | 239 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Coding Agentmastra-ai/mastra | 29k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Code ReviewerYikai-Liao/symusic | 189 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Typescript React ReviewerSuFxGIT/scoutarr | 114 | — | ~1.7k | Automated safety check: Pass | None | |
| Memtrace Change Impact Analysissyncable-dev/memtrace-public | 486 | — | ~1.4k | Automated safety check: Pass | Custom licence |
Similar skills
Coding Agent
mastra-ai/mastra
Authoring playbook for building agents that write, edit, review, or refactor code.
Code Reviewer
Yikai-Liao/symusic
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then…
Typescript React Reviewer
SuFxGIT/scoutarr
Expert code reviewer for TypeScript + React 19 applications.
Memtrace Change Impact Analysis
syncable-dev/memtrace-public
Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated…
Develop Microfeed
microfeed/microfeed
Develop and contribute changes to the microfeed repository safely from branch creation through validation, commit, push, and draft pull request.
More from timmo001/system-bridge
All 12 skills in this repoWriting Style
timmo001/system-bridge
Write commit messages, PR and issue text and comments, docs (README), code comments, and user-facing strings (notifications, UI labels, toasts, error messages) in the project owner's voice: concise…
System Bridge Go Backend
timmo001/system-bridge
System Bridge Go backend conventions - error wrapping, graceful degradation for data modules, nil-pointer safety, context-aware Module.Update, structured slog logging, and errcheck-clean deferred…
System Bridge Testing Workflow
timmo001/system-bridge
How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket…
System Bridge Troubleshooting
timmo001/system-bridge
Known System Bridge build and runtime failures and their fixes, plus per-OS token/log/settings/data file locations.
System Bridge Docs Page Workflow
timmo001/system-bridge
Add or restructure a page in the System Bridge Astro + Starlight docs site under docs/ - create the content file, set frontmatter, and wire the sidebar.
System Bridge Landing Content Updates
timmo001/system-bridge
Update the System Bridge marketing landing page in the Astro + Starlight docs site.
Related
Categories
Questions about Changeset Scope
What does Changeset Scope do?
Keep all scoped code work contained to the user-defined changeset. Changeset Scope is an agent skill from timmo001/system-bridge. Keep all scoped code work contained to the user-defined changeset.
When should I use Changeset Scope?
Changeset Scope fits situations like: review when explicit instructions; injected work scopes define the boundary.
How do I install Changeset Scope in Claude Code?
Run `npx skills add timmo001/system-bridge --skill changeset-scope -a claude-code`. Or copy the skill folder (.agents/skills/changeset-scope in timmo001/system-bridge) into .claude/skills/changeset-scope in your project. Claude Code loads it when a task matches its description.
How do I install Changeset Scope in Codex?
Run `npx skills add timmo001/system-bridge --skill changeset-scope -a codex`. Or copy the skill folder (.agents/skills/changeset-scope in timmo001/system-bridge) into .agents/skills/changeset-scope in your project. Codex loads it when a task matches its description.
Can I use Changeset Scope in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add timmo001/system-bridge --skill changeset-scope -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changeset-scope, .gemini/skills/changeset-scope, .github/skills/changeset-scope and .opencode/skills/changeset-scope in your project.
What does Changeset Scope need to run?
SKILL.md names no scripts, command-line tools or credentials: Changeset Scope is instructions for the agent only.
Does Changeset Scope access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Changeset Scope safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Changeset Scope use?
Changeset Scope is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Changeset Scope use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Changeset Scope?
Skills that share tags, products or a category with Changeset Scope: Smell Check (Zhen-Bo/smell-check, 239 stars), Coding Agent (mastra-ai/mastra, 29k stars), Code Reviewer (Yikai-Liao/symusic, 189 stars) and Typescript React Reviewer (SuFxGIT/scoutarr, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changeset Scope?
timmo001 (a GitHub user) maintains it in timmo001/system-bridge, which has 356 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.
Source: timmo001/system-bridge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.