Adding "Stealth Mode" for External Repositories - #16
Conversation
PR SummaryMedium Risk Overview
Core skills ( Written by Cursor Bugbot for commit d1dea43. This will update automatically on new commits. Configure here. |
| fi | ||
| fi | ||
| fi | ||
| } |
There was a problem hiding this comment.
Stealth ensure_dir skips exclude for pre-existing directories
Low Severity
The ensure_dir function only adds a directory wildcard pattern (e.g. docs/core/*) to .git/info/exclude when the directory is being newly created. In company repos where directories like docs/core/, .cursor/skills/, or .github/ already exist, no wildcard exclusion is added. While individually synced files get per-file exclusions, any additional files the AI creates later in those directories during development won't be covered.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.


🏷️ Type of Change
📝 Summary
This PR introduces Stealth Mode, a structural configuration that allows developers to run
agentic:guildinside external, locked-down, or team-owned repositories without leaving visible traces or forcing the AI's preferred structure onto the rest of the development team.When initialized with
sync.sh --stealth, the Operating System fundamentally shifts how its skills operate. It relies on local exclusions (.git/info/exclude instead of.gitignore), heavily restricts automatic documentation mutations, and suppresses internal compliance trackers like[REQ-ID]tags that would otherwise pollute a team's clean git workflow.✨ Key Changes
--stealthinstallation flag. Installer now securely registers internal directories strictly to .git/info/exclude, skips Git Hook installation, and conditionally avoids scaffolding the heavydocs/*directory trees to prevent dirtying external filesystems.update-agentic-guild: The updater skill is now entirely stealth-aware. It registers new upstream files directly to .git/info/exclude, skips merging conflicts on team-tracked files (e.g., PR templates), and now automatically disposes of thetmp_updaterepository clone after summarizing the newest upstream changelog.start-task&audit-compliance: Conditioned the Construction-by-Contract (CbC) instructions and IV&V Audit checks to ignore[REQ-ID]traceability entirely when in stealth mode, ensuring external repos remain clean of internal metadata tags.finish-branch: Conditioned the final PR phase to entirely skip executing thesync-docsandharvest-rulesskills in stealth mode, and explicitly prevents the AI from attempting to modify or checkdocs/ROADMAP.mdorCHANGELOG.md.pr-description: Updated the drafting prompt to generate a standard, open-source style PR description if in stealth mode, stripping any mention of agentic:guild's internal structures.📸 Screenshots / Videos (if applicable)
N/A
🧪 Verification Plan
Automated Tests
Manual Verification
sync.sh --stealthin a clean directory and confirm .git/info/exclude contains the accurate exclusions without a!.agenticguild/.gitkeepun-exclude.--stealthflag and resets.agenticguild/config.jsonto false.update-agentic-guildcorrectly skips creating.cursorrulesif it doesn't already exist and appropriately adds it to stealth exclusions if it does.<phase id="0" name="Stealth Check">during execution runs.🛡️ Impact Assessment
🧠 Anti-Drift Checklist
To prevent "drift" between the codebase and our AI context, please attest that you have updated the authoritative documentation:
sync-docsand updated any docs that require changes (SPEC, schema, DATA_FLOW_MAP, ADRs, etc.).docs/ROADMAP.mdhas been updated (finish-branch does this automatically).docs/core/ADRs/if new paradigms were introduced..cursorrulesor approved aharvest-rulesrun if developer protocols changed.docs/core/SYSTEM_ARCHITECTURE.mdif the tech stack, libraries, or core patterns shifted.🔍 Reviewer Focus Areas
Special attention on the ensure_dir exclusion refactor in sync.sh. We transitioned from a wildcard directory paradigm (which was overwriting valid team files) to a rigorous file-by-file exclusion model.
🔜 Follow-ups / PENDING
None.