Absorbs Git pull changes and emits a concise briefing from HANDOFF/RUNNING scans.
npx skills add https://github.com/ScavieFae/autonomous-world-model --skill pull-scaviefae
Please help me install this Agent Skill. Skill: pull Source: https://github.com/ScavieFae/autonomous-world-model/tree/main/.claude/skills/pull Command: npx skills add https://github.com/ScavieFae/autonomous-world-model --skill pull-scaviefae
Post-pull orientation — absorb what changed, scan HANDOFF and RUNNING for new context, check run cards and program.md, report to user. Use when starting a session, after a git pull, or when the user says "pull", "catch me up", or "what changed", or "orient".
Run the pull workflow after a git pull or when the user says pull to absorb changes and align context.
High-intent search queries and answers about installing and using this skill.
Reorient your workspace after a git pull by scanning HANDOFF and RUNNING contexts, run cards, and program.md to absorb changes. This process generates a concise briefing summarizing what landed and updates the last-pull state to guide your next session.
The best way to catch up on project context at session start is to run a read-heavy workflow that digests new docs and run cards. It aligns your context by producing a concise briefing of recent changes and reestablishing the current state.
Context synchronization after pulling works by orchestrating HANDOFF and State scanners to digest new documents and run cards. It enforces a deterministic workflow that outputs a concise briefing and updates last-pull state for future reference.
Yes, you can get a summary of recent changes without manual file reading. The workflow scans HANDOFF and RUNNING contexts, run cards, and program.md to automatically generate a concise briefing of what changed and what needs attention.
No, this post-pull orientation workflow does not require external dependencies or components. It operates independently by scanning existing project context files like HANDOFF docs, run cards, and program.md to produce its briefing.
You should run a workspace orientation workflow when starting a session, immediately after a git pull, or when you need to catch up on changes. It aligns your context by absorbing what landed and updating the last-pull state.
az9713Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.
MichelKerkmeesterOrchestrate frontend code-quality workflows across implementation, debugging, and verification phases.
theslashdojoManage git remotes and synchronize local branches with remote refs.
OlshanskGenerate manual test plans for pull request changes with pass/fail criteria.
