pdda-hook

Adds session hooks to enforce project-driven documentation rules and remind agents to read key files.

2|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill pdda-hook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdda-hook
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/SKILLS/PDDA-hook
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill pdda-hook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

This skill solves the issue of AI agents forgetting project-governance rules over long sessions by providing a deterministic, persistent reminder system that re-anchors the agent to the project's documentation contract.

Core Features & Use Cases

  • SessionStart Reminders: Automatically injects a PDDA compliance reminder whenever a session context resets, ensuring the agent remains aware of the required read-order for ROUTER.md and AGENTS.md.
  • Optional PreToolUse Gate: Provides an opt-in enforcement mechanism that prevents edits to governed project files unless the agent has demonstrably read the project's router documentation.
  • Use Case: A developer working across multiple repositories can use this to ensure that every time they resume a session, the AI is immediately reminded to follow the specific project-driven documentation standards defined in the local repository.

Quick Start

Ask the assistant to set up the PDDA hook to ensure all future sessions follow the project documentation governance rules.

Frequently Asked Questions about pdda-hook

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

FAQPage Schema
How do I enforce documentation governance rules for AI agents across long coding sessions?

The hook works by detecting a session context reset and automatically injecting a PDDA compliance reminder, which re-anchors the agent to the project's documentation contract without relying on memory.

How do I set up automated hooks to prevent AI from editing project files before reading the router documentation?

This opt-in enforcement mechanism verifies transcript history to enforce contract-based workflows deterministically, independent of session memory.

Do I need git and jq installed to automate session-start hooks for project-driven documentation?

These tools enable deterministic, non-memory-dependent compliance by checking repository state and parsing configuration data.

Why does my AI agent forget repository-specific documentation standards when resuming a session?

It detects when a session context resets and immediately injects the required project-driven documentation standards defined in the local repository.

What are the limitations of using session-start hooks for documentation compliance?

Additionally, the hook operates across diverse development environments by detecting the presence of project-specific documentation, so it only applies reminders or edit-gates if those specific files exist.