session-archaeologist

Detect hidden patterns and contradictions in project histories and configurations.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/jarrett-au/autoplug --skill session-archaeologist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-archaeologist
Source: https://github.com/jarrett-au/autoplug/tree/main/plugins/agent-evolve/skills/session-archaeologist
Command: npx skills add https://github.com/jarrett-au/autoplug --skill session-archaeologist

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users discover subconscious patterns, biases, and contradictions within project history and configurations, providing insights that are hard to notice manually.

Core Features & Use Cases

  • Deep Pattern Mining: Analyzes project memory, code history, and configuration files to reveal underlying behaviors and hidden structures.
  • Contradiction Detection: Identifies inconsistencies and conflicting patterns in development practices, commit history, and system setups.
  • Use Case: A developer notices inconsistent code quality and wants to uncover whether this stems from evolving tools or inconsistent practices over time.

Quick Start

Ask the AI to analyze project history and configurations to uncover patterns and contradictions to improve understanding.

Frequently Asked Questions about session-archaeologist

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

FAQPage Schema
How do I detect hidden patterns and contradictions in project history?

To detect hidden patterns and contradictions in project history, you analyze version control commits, directory structures, and configuration files to reveal underlying behavioral patterns and implicit system structures.

What causes inconsistent code quality across version control commits?

Inconsistent code quality across version control commits stems from evolving tools or conflicting development practices, which you can uncover by mining historical decision records and detecting contradictions in project configurations.

How do I analyze project configurations to find conflicting development practices?

You analyze project configurations by applying contradiction detection to textual configuration data and historical decision records, identifying inconsistencies and conflicting patterns in system setups and development practices.

Does pattern mining work for analyzing directory structures and code history without external dependencies?

Yes, pattern mining works without external dependencies by directly analyzing your existing code history, directory structures, and textual configuration data to generate strategic insights and reveal hidden structures.

When should I use contradiction detection for configuration review?

You should use contradiction detection for configuration review when you notice inconsistent code quality or system behaviors, helping you uncover subconscious patterns and biases that are hard to notice manually.