What problem does it solve? When an agent commits and pushes a brain page, users often receive a report with no link, a broken link, or a raw local path they cannot click. This Skill enforces a reporting discipline where every message that reports a created, edited, or relayed brain page includes a working link in the same message, derived mechanically from git data rather than guessed. ## Core Features & Use Cases - Mechanical path derivation: Builds repo-relative paths with git ls-files --full-name and assembles hosted URLs from git remote get-url origin, eliminating hand-stripped prefixes that cause 404s. - Push-before-link ordering with verification: Requires the push to land and the ref update to be confirmed (or an HTTP existence check against the hosted remote) before any URL is sent, with a defined fallback chain for local-only repos. - Subagent relay rewriting and scope split: Rewrites local paths returned by subagents into user-facing links, and enforces the inversion rule — relative links inside brain pages to preserve the links/backlinks graph, absolute verified URLs only in chat messages. - Use Case: After committing three new people pages, the agent replies in the same message with one verified GitHub link per page, or falls back to repo-relative paths plus a gbrain publish HTML artifact offer when no hosted remote exists. ## Quick Start Report the brain pages you just committed and include a working clickable link for each one in the same message.
