foxctl-context

Bundle context architecture surfaces and transcript-derived continuity into a single pack.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl-context
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-context
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of rebuilding accurate, decision-useful development context by bundling context architecture surfaces, transcript-derived continuity, and knowledge-layer bridges into one coherent pack.

Core Features & Use Cases

  • Context architecture bundling: Packages current context/architecture surfaces so operators and agents share a consistent view of what matters now.
  • Transcript history ingest and lane summarization: Derives brief timelines, notable insights, and structured history packs from persisted transcript history, optionally scoped to focus queries or dates.
  • ContextWiki/Obsidian knowledge-layer workflows: Supports indexing, graph builds, promotion, and bridge reconciliation to keep durable notes aligned with repo/lane changes.
  • Refactor scouting close to the same context seam: Finds and advises refactor hotspots when structural cleanup is part of the same context work, rather than an unrelated later activity.

Quick Start

Run foxctl context family-history-summary --workspace . --focus-query "recursive memory second-pass consolidation transcript pipeline" to get a bounded lane summary from your persisted transcript history.

Frequently Asked Questions about foxctl-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore development context from transcript history after a long break?

Transcript history continuity restores development context by packaging context-architecture surfaces and deriving lane summaries from persisted transcripts, bundling them into a single coherent pack for actionable reuse.

Can I sync a ContextWiki or Obsidian knowledge graph with current repository changes?

Knowledge-layer syncing aligns ContextWiki or Obsidian notes with repository changes by supporting indexing, graph builds, promotion, and bridge reconciliation to keep durable notes updated.

How does focus-query and date-bounded filtering work for transcript summarization?

Focus-query and date-bounded filtering scope transcript-derived lane summaries to specific topics or timeframes, generating bounded timelines and notable insights from persisted history.

What is refactor scouting and when should I use it during context work?

Refactor scouting finds and advises structural cleanup hotspots within the same context seam, ensuring alignment with current work rather than treating refactoring as an unrelated later activity.

Do I need to persist transcript history before generating lane summaries?

Yes, generating lane summaries requires transcript history to be persisted first, ensuring the continuity outputs and timelines are derived from complete historical data before bundling.

What's the best way to package context architecture surfaces for agents and operators?

Context architecture bundling packages current surfaces so operators and agents share a consistent view, combining these surfaces with transcript-derived continuity into one reusable pack.