jaredchu/context-docs / skills/context-docs
context-docs
VerifiedCreate, audit, and maintain project context documents and Markdown progress views for continuity across AI sessions. Use when establishing context conventions, refreshing project state, visualizing progress toward a documented goal, or consolidating stale context. Adapt to existing layouts and preserve decisions and evidence. Not for general copyediting or storing conversation transcripts.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 10.1 KB |
| VERSION | other | 6 B |
| agents/openai.yaml | config | 224 B |
| assets/decision-record.md | markdown | 724 B |
| assets/project-context.md | markdown | 1.1 KB |
| references/event-journal.md | markdown | 13.3 KB |
| references/local-only.md | markdown | 5.9 KB |
| references/progress.md | markdown | 9.1 KB |
| references/standard.md | markdown | 9.1 KB |
| scripts/event_journal.py | script | 8.7 KB |
| scripts/journal_policy.py | script | 10.9 KB |
assets/project-context.md
View on GitHub# Project context
<!-- Starter only. Adapt names to the existing project. Replace prompts with
supported facts for the intended readers and sharing destination. Keep detailed
procedures, historical evidence and incidental local state in their appropriate
existing locations; link when useful. Remove unused sections and these comments
before adopting. -->
## Purpose and scope
<!-- Identify the project, intended outcome, and important boundaries. -->
## Current state
<!-- Describe verified behavior and active work. Date time-sensitive observations
and link to evidence. Mark deployment state unknown if only code was checked. -->
## Decisions and constraints
<!-- Record approved choices with rationale and authority/source, or link to the
canonical decision record. Keep proposed changes explicitly separate. -->
## Open questions and next actions
<!-- Describe meaningful unresolved work, its next step, and any blocker. -->
## Canonical references
<!-- Link to existing procedures, focused docs and useful historical evidence.
Use repository-relative links; do not duplicate the linked content. -->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |