Projects
RepoLens RAG
Portfolio project record for repository-focused retrieval and codebase explanation workflows.
Summary
- Targets repository reading, summarization, and traceable answer generation.
- Evidence remains at concept/prototype level until runnable artifacts are linked.
Problem
- Codebase Q&A needs traceable retrieval and source-grounded summaries rather than unverified answer generation.
- Benchmark evidence is not present, so capability claims must stay at concept/prototype level.
Approach
- Represent the project as a repository analysis workflow with explicit retrieval, citation, and review checkpoints.
- Keep benchmark and runnable artifact links as pending until verified reports are available.
Evidence artifacts
Workflow noteworkflow
Cataloged as a repository-analysis workflow; public benchmark evidence is not present.
No verified URL attached
Benchmark TBDbenchmark
No benchmark report has been verified.
No verified URL attached
Proof boundary
Missing public proof stays visible here as TBD, pending, planned, prototype, research, or note-style evidence. SkillDex does not turn unverified artifacts into proof links.
Related skills
Related skills are navigation and workflow-capability links. They do not replace evidence artifacts and should not be read as proof that a project is shipped.
- activeProject ManagementMy skillVibe Coding Review
A personal project-governance Skill for keeping AI-assisted coding work aligned with project briefs, active phases, review gates, and explicit non-goals.
- activeCodingOther skillMCP Builder
A Claude Skill for designing and implementing MCP servers with clear tool names, schemas, transports, and evaluation coverage.
Next steps
- Add a small reproducible repository fixture before presenting benchmark results.
- Link a benchmark report only when the methodology and output are public and reviewable.