prior-art

Analyze a codebase to discover how a specific concern is handled.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/vonchristian/sirib --skill prior-art-vonchristian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prior-art
Source: https://github.com/vonchristian/sirib/tree/main/.opencode/skills/prior-art
Command: npx skills add https://github.com/vonchristian/sirib --skill prior-art-vonchristian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit helps identify how a specific concern is addressed within a codebase, enabling developers to understand patterns and inconsistencies.

Core Features & Use Cases

  • Search Across Codebase: Identifies all instances where a concern is handled, including keywords, common Rails locations, and the Gemfile.
  • Git History Analysis: Provides insights into the evolution of patterns over time, using Git commands to view recent changes and commits related to the concern.
  • Mapping and Reporting: Summarizes the patterns, conventions, inconsistencies, and Git context, and suggests how to extend the patterns.

Quick Start

Use the prior-art skill to analyze how the codebase handles authentication.

Frequently Asked Questions about prior-art

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

FAQPage Schema
How do I analyze a codebase to find how a specific concern is handled?

Codebase analysis for specific concerns uses multiple search strategies, checking keywords, common Rails locations, and the Gemfile to map patterns and inconsistencies. It summarizes conventions and suggests how to extend existing patterns.

Can I use Git history to track the evolution of code patterns over time?

Git history analysis tracks the evolution of code patterns by viewing recent changes and commits related to the concern. It provides insights into how specific handling conventions developed within the codebase.

Does this codebase review tool work with Rails applications?

Yes, codebase review specifically checks common Rails locations and the Gemfile to identify concern handling. It requires access to the codebase and Git to perform comprehensive pattern identification and reporting.

What is the best way to identify inconsistencies in how a concern is addressed across a project?

Identifying inconsistencies requires mapping and reporting across the codebase using multiple search strategies. It summarizes discovered patterns, conventions, and Git context to reveal how a specific concern is handled.

Do I need Git access to perform a codebase review for pattern identification?

Yes, Git access is required for comprehensive codebase review and pattern identification. Git history analysis provides necessary insights into recent changes and commits related to the specific concern being evaluated.