Skip to content

fix(#1939): add prominent protected-paths section to fix agent #1940

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralphbean merged 1 commit into from
Jun 8, 2026
Merged

fix(#1939): add prominent protected-paths section to fix agent #1940

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 30 additions & 4 deletions internal/scaffold/fullsend-repo/agents/fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,34 @@ bot feedback — but still verify against the code. A human instruction to
"revert the change to function X" should be verified: does the function exist?
Was it actually changed?

## Protected paths — do not modify

Never modify files under any of the following paths, even if they appear in
merge conflicts, linter suggestions, or other incidental context:

- `.claude/` — agent settings and configuration
- `.cursor/` — editor agent configuration
- `agents/` — agent definitions
- `harness/` — harness definitions
- `plugins/` — plugin definitions
- `policies/` — sandbox policies
- `scripts/` — pre/post scripts
- `api-servers/` — API server configurations
- `.github/workflows/` — CI configuration
- `CODEOWNERS`
- `.pre-commit-config.yaml`
- `.gitattributes`

These are governance and infrastructure files. The `post-fix.sh` safety
script blocks commits that touch them, discarding **all** of your work —
including legitimate code fixes. Modifying these paths wastes the entire
run.

The only exception is when a human `/fs-fix` instruction **explicitly** asks
you to modify a specific protected path. Even then, the post-script may
still block the change — but following a direct human instruction is
acceptable.

## Constraints

- Keep changes minimal. Every line in your diff must be traceable to a specific
Expand All @@ -103,10 +131,8 @@ Was it actually changed?
files you explicitly created or modified.
- You cannot use `sed`, `awk`, or other stream editors to modify source files.
Use the `Write` tool for all file edits.
- You cannot modify CODEOWNERS files, CI configuration in `.github/workflows/`,
agent configuration in `.claude/` or `agents/`, harness definitions in
`harness/`, sandbox policies in `policies/`, pre/post scripts in `scripts/`,
or API server configurations in `api-servers/`.
- You cannot modify protected-path files (see "Protected paths" above) unless
a human `/fs-fix` instruction explicitly asks you to.
- Always create a **new commit**. Never amend an existing commit.
- If a review finding suggests a change that is out of scope for this PR
(e.g., a refactoring suggestion unrelated to the PR's purpose), record it
Expand Down
Loading