Terms that change how you work
- Scope
- The boundary of the task: what should change and what should remain untouched.
- Context window
- The information a model can consider in a session. Files, logs, prompts, and conversation share that space; more text is not always more useful context.
- Sandbox
- An isolated environment with limited permissions for commands, files, or network access. Its protection depends on the actual permissions granted.
- Skill
- Reusable specialised instructions for a kind of work, including what to read, which tools to use, and how to verify.
- MCP
- Model Context Protocol: a standard through which AI applications can discover and use tools or data exposed by compatible servers.
- Worktree
- A second working directory linked to the same Git repository, allowing parallel branches without mixing working files.
- CI
- Continuous Integration: automated checks such as build, tests, lint, or security scans run when changes are proposed or pushed.
- Branch
- A Git reference for a line of work. It isolates commit history, not automatically the working directory.
- Pull request
- A proposed merge that gathers a diff, discussion, review, and checks before integration.
- Rollback
- A planned way back to a working state when a change causes problems.
A small feature uses all of them
Imagine adding an “updated articles only” filter. Its scope covers the control, state, and resulting list, not a whole-page redesign. A dedicated branch holds the commits; a worktree can keep the files separate from another ongoing change.
Give the agent the list component, data model, and relevant tests rather than the entire repository. The sandbox limits what it can touch; a skill can describe a repeatable verification workflow; MCP should be used only if external data or tools are actually needed. Then inspect the diff, run checks, open a PR, and let CI repeat configured checks.
Task path
scope -> branch/worktree -> relevant context -> sandbox
-> skill/MCP if needed -> diff -> tests/build
-> commit -> pull request -> CI -> merge
-> monitor -> rollback if neededQuestions behind reassuring words
- “It ran in a sandbox”: which files, commands, and network destinations were allowed?
- “More context helps”: did the extra material hide the important instructions?
- “CI is green”: which behaviours do those jobs actually test?
- “The change is isolated”: in which branch or worktree is the diff?
- “We can roll back”: what exact procedure and data would that involve?
Primary references
These are working definitions. Read the official Git, GitHub, and MCP documentation for precise behaviour and current limitations.