prime

Collects docs, code structure, and git history to synthesize a plan with files and risks.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill prime-masta-g3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prime
Source: https://github.com/masta-g3/rules/tree/main/skills/prime
Command: npx skills add https://github.com/masta-g3/rules --skill prime-masta-g3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context priming surfaces the necessary information, docs, and history before you begin work, reducing guesswork and rework.

Core Features & Use Cases

  • Collects and organizes repo structure, docs references, and recent history to inform task planning.
  • Coordinates lightweight, read-only scouting of code areas when tasks span multiple modules.
  • Produces a concise synthesis of files to touch, patterns to follow, and risks to consider.

Quick Start

Describe the task to prime and gather contextual resources before execution.

Frequently Asked Questions about prime

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

FAQPage Schema
How do I gather project context before starting a coding task?

Context priming gathers project context by reading docs, checking git history, and locating relevant modules to reduce guesswork. It synthesizes files to touch, patterns to follow, and risks before task execution.

Why does my codebase planning miss recent git history changes?

Codebase planning often misses changes when it skips git history analysis. Reviewing recent commits before execution surfaces up-to-date context, preventing rework and ensuring the plan reflects the current state of the project.

What is the best way to identify risks and files to touch before executing a multi-step task?

Identifying risks and files to touch requires synthesizing repo structure and docs references. Read-only scouting of code areas produces a concise plan that highlights modules to modify and potential risks.

How do I use docs and code structure to inform task planning?

Inform task planning by reading docs like STRUCTURE.md and organizing repo structure. This coordinates lightweight scouting across modules, producing a synthesis of patterns to follow and files to modify.

Does context priming work for multi-module code projects?

Context priming works for multi-module code projects by coordinating lightweight, read-only scouting of code areas. It organizes repo structure and docs references to ensure accurate planning for tasks spanning multiple modules.

When should I not use context priming for task planning?

Context priming should not be used for simple, single-file edits where up-to-date context is non-essential. It applies to multi-step tasks where synthesizing git history and code structure is necessary to prevent rework.