You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR introduces a robust onboarding experience for new users and a proactive update notification system for existing users. It establishes an "Anti-Vibe-Coding" safeguard that guides users who write unstructured prompts towards using strict architectural workflows. It also leverages the AI's natural conversation during standard workflow GPS checks (explore-task, start-task, status-check) to passively alert the user if a new version of agentic:guild is available upstream without relying on background cron jobs.
✨ Key Changes
"Who are you?" Onboarding Skill: Created skills/hello/SKILL.md to introduce the agent, assess the project's health by checking for core architectural documents, and provide a menu of copy-paste triggers.
Terminal Call-to-Action: Updated sync.sh to print a highly visible call-to-action recommending the user trigger the new hello skill upon installation completion.
Anti-Vibe Coding Safeguard: Added an <onboarding> directive to templates/core/AGENTIC_GUILD_RULES.md that intercepts raw, unstructured prompts and routes the user into either explore-task or start-task.
Proactive Update Notifications: Added an <update_check> hook inside the pre-flight sequence for skills/explore-task/SKILL.md, skills/start-task/SKILL.md, and skills/status-check/SKILL.md. This silently fetches the upstream package.json and compares it to a localized copy of the package (.agenticguild/source_package.json), dropping an update banner into the chat if the upstream is higher or the local file is missing.
Sync Registry Expansion: Updated playbooks/SYNC_REGISTRY.md to track the package.json and map the new hello skill for future synchronized updates.
Bugbot Fixes: Standardized the hello skill XML schema to perfectly match the <agentic_guild_skill> template across other skills and patched a logic flaw in the missing file handling for version updates.
📸 Screenshots / Videos (if applicable)
N/A
🧪 Verification Plan
Automated Tests
N/A
Manual Verification
[User opens a fresh project and runs sync.sh: verifies they see the output urging them to type "Who are you?"]
[User types "Who are you?": verifies the hello skill executes and runs the structural document checks.]
[User types a raw prompt like "build a login page": verifies AGENTIC_GUILD_RULES.md correctly steps in and routes them to explore-task or start-task.]
[User runs status-check, explore-task, or start-task with a missing or outdated local version of package.json: verifies the update notification appears natively in the response.]
🛡️ Impact Assessment
Security: No impact
Performance: No impact
Accessibility: No impact
🧠 Anti-Drift Checklist
To prevent "drift" between the codebase and our AI context, please attest that you have updated the authoritative documentation:
Docs: I have run sync-docs and updated any docs that require changes (SPEC, schema, DATA_FLOW_MAP, ADRs, etc.).
Roadmap: If this PR completes a roadmap item, docs/ROADMAP.md has been updated (finish-branch does this automatically).
Architecture (ADR): I have created/updated ADRs in docs/core/ADRs/ if new paradigms were introduced.
AI Rules: I have updated .cursorrules or approved a harvest-rules run if developer protocols changed.
Boundaries: I have updated docs/core/SYSTEM_ARCHITECTURE.md if the tech stack, libraries, or core patterns shifted.
🔍 Reviewer Focus Areas
Verify that all XML updates in the <update_check> hooks explicitly instruct the AI not to block the underlying workflow task execution.
Low Risk
Low risk: changes are limited to agentic:guild workflow docs/skills and installer messaging, with no application/runtime code paths affected. Main risk is behavioral (new intent routing and optional version-check notices) potentially altering how the assistant responds to prompts.
Overview
Adds a new hello skill that introduces agentic:guild, checks for required core docs, and provides copy/paste next-step commands; it’s now synced via SYNC_REGISTRY.md and routed from .cursorrules when users ask “who are you/what is agentic guild/how do I start”.
Adds an upstream update check to start-task, explore-task, and status-check, comparing package.json version from GitHub to a locally-synced .agenticguild/source_package.json and displaying a “new version available” notice when applicable.
Updates sync.sh to print a post-install onboarding hint, and extends onboarding rules in AGENTIC_GUILD_RULES.md to steer unstructured prompts into start-task/explore-task (anti-vibe-coding safeguard).
Written by Cursor Bugbot for commit 5a70406. This will update automatically on new commits. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🏷️ Type of Change
📝 Summary
This PR introduces a robust onboarding experience for new users and a proactive update notification system for existing users. It establishes an "Anti-Vibe-Coding" safeguard that guides users who write unstructured prompts towards using strict architectural workflows. It also leverages the AI's natural conversation during standard workflow GPS checks (
explore-task,start-task,status-check) to passively alert the user if a new version ofagentic:guildis available upstream without relying on background cron jobs.✨ Key Changes
helloskill upon installation completion.<onboarding>directive to templates/core/AGENTIC_GUILD_RULES.md that intercepts raw, unstructured prompts and routes the user into eitherexplore-taskorstart-task.<update_check>hook inside the pre-flight sequence for skills/explore-task/SKILL.md, skills/start-task/SKILL.md, and skills/status-check/SKILL.md. This silently fetches the upstream package.json and compares it to a localized copy of the package (.agenticguild/source_package.json), dropping an update banner into the chat if the upstream is higher or the local file is missing.helloskill for future synchronized updates.helloskill XML schema to perfectly match the<agentic_guild_skill>template across other skills and patched a logic flaw in the missing file handling for version updates.📸 Screenshots / Videos (if applicable)
N/A
🧪 Verification Plan
Automated Tests
Manual Verification
helloskill executes and runs the structural document checks.]explore-taskorstart-task.]status-check,explore-task, orstart-taskwith a missing or outdated local version of package.json: verifies the update notification appears natively in the response.]🛡️ 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
Verify that all XML updates in the
<update_check>hooks explicitly instruct the AI not to block the underlying workflow task execution.🔜 Follow-ups / PENDING
None