skills.rest
meisijiya
meisijiyaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

read-project-context

Read CONTEXT.md, AGENTS.md, ADRs, and gotchas to recover project conventions.

Updated Aug 23, 2026
Search Tags:#documentation#adr#conventions#project context#gotchas#repository memory
One-click install
npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill read-project-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: read-project-context
Source: https://github.com/meisijiya/ohMeisijiyaCode/tree/main/skills/read-project-context
Command: npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill read-project-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand a repository’s project memory, conventions, and architectural history before making decisions or touching code.

Core Features & Use Cases

  • Project Vocabulary Lookup: Reads context files to clarify domain terms, naming conventions, and relationship definitions.
  • Architectural Decision Review: Surfaces prior decisions and constraints from ADRs before proposing changes.
  • Pitfall Awareness: Checks known gotchas so you can avoid repeating project-specific mistakes.
  • Use Case: When a teammate asks why a pattern exists or you are about to change an unfamiliar area, use this Skill to load the relevant project context first.

Quick Start

Use the read-project-context skill to inspect the repository’s context files and summarize the conventions, decisions, and pitfalls that matter for my current task.

Frequently Asked Questions about read-project-context

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

FAQPage Schema
How do I read project context and architectural decisions before modifying an unfamiliar repository?▼

Review architectural decisions by examining ADR files located in docs/adr. This surfaces prior constraints and historical design choices, ensuring your proposed changes align with established architectural patterns and project-specific conventions.

What is the best way to check repository conventions and known gotchas before starting a session?▼

The best way to check repository conventions is performing a skim-first load of context files like CONTEXT.md and docs/gotchas. This read-only inspection quickly surfaces project memory, domain terms, and known pitfalls to prevent repeating mistakes.

Can I look up project vocabulary and domain terminology on demand during a coding session?▼

Yes, you can look up project vocabulary on demand by reading context files. The process requires read-only inspection of files like AGENTS.md to clarify domain terms, naming conventions, and relationship definitions across initialized repositories.

Does this project context reader work with uninitialized repositories?▼

No, this project context reader does not work with uninitialized repositories. It performs initialization checks and requires existing context files like CONTEXT.md, AGENTS.md, docs/adr, and docs/gotchas to successfully load project memory.

When do I need to load repository memory and ADRs for pre-change planning?▼

You need to load repository memory and ADRs whenever a teammate asks why a pattern exists or you are about to change an unfamiliar code area. Reading context files first ensures your pre-change planning respects historical architectural decisions.

Related Skills

Explore More Software Engineering Skills→
spenceriamspenceriam
1

planner

Generate AGENTS.md and docs/Requirements.md, Design.md, and Tasks.md for greenfield projects.

Community
Advanced
alissonpefalissonpef

documentation-and-adrs

Record architectural decisions and update project documentation for codebases.

Community
Intermediate
Fandhe-AIFandhe-AI
1

update-docs

Update CLAUDE.md documentation from Git commit changes.

Official
Intermediate
vanillacake369vanillacake369
2

codebase-analysis

Analyze unfamiliar codebases to extract patterns, conventions, and technology stack.

Community
Basic