Generate a scoped context briefing for JellyRock code subsystems.
npx skills add https://github.com/jellyrock/jellyrock --skill ramp-jellyrock
Please help me install this Agent Skill. Skill: ramp Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/ramp Command: npx skills add https://github.com/jellyrock/jellyrock --skill ramp-jellyrock
This Skill eliminates the tedious manual work of gathering scattered context when switching to a JellyRock code subsystem you haven't touched in over 2 weeks, saving you hours of sifting through commit history, documentation, tech debt records, and open issues.
Invoke the ramp skill with your target JellyRock subsystem name such as components/video or source/api to generate a full scoped context briefing for that area.
High-intent search queries and answers about installing and using this skill.
Codebase onboarding for an inactive subsystem is handled by aggregating scoped project state, recent commits, and area-specific rules into a structured briefing. This eliminates manual context-gathering by delivering architecture docs, tech debt records, and recommended entry point files for immediate productive work.
Git history aggregation and tech debt tracking are combined to pull recent commits, open issues, and pending handoffs filtered specifically to your target area. This scoped state aggregation ensures you receive only the relevant activity and debt records for your subsystem.
Area-scoped rules and documentation are auto-loaded for recognized subsystems including components, source, tests, locale, and scripts. The briefing retrieves matching CLAUDE.md guidelines and architecture topic docs specific to the requested folder.
Context switching after a two week break does not require manual issue review because the briefing automatically aggregates open issues and PRs filtered to your target subsystem. This provides a complete view of pending work and relevant recent activity.
A subsystem briefing includes area-specific guidelines, architecture documentation, tech debt records, recent commits, open issues, related skills and agents, and recommended entry point files. This structured context enables immediate productive work without manual searching.
Entry point files are identified through related resource discovery during the briefing generation. The aggregation process analyzes the subsystem to recommend the top files to read first, ensuring you start reading the most relevant source code immediately.
JadeZaherManage ecosystem participant lifecycle states and onboarding consent ceremonies.
ben-mad-jlpCollects and classifies work items into types for a collaborative coding session.
me2reshCollect per-project git state, pull requests, and CI check rollups.
romiluz13Generate a dated Markdown status report across active Pi sessions.
