mirror of
https://github.com/documenso/documenso.git
synced 2026-07-10 13:06:00 +10:00
960217c78d
- Switch package manager to pnpm 10 via corepack - Add pnpm-workspace.yaml with 54+ shared dependency catalogs - Convert all workspace packages to catalog: and workspace:* protocols - Upgrade Turborepo from 1.x to 2.8.12 (pipeline -> tasks) - Upgrade apps/openpage-api from Next 15 to Next 16 - Update Docker, CI workflows, and GitHub Actions for pnpm - Convert patch file to pnpm native format - Replace deprecated next lint with standalone eslint - Update all documentation references from npm to pnpm - Fix stale dependabot config and documentation paths
1.9 KiB
1.9 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Create a new justification file in .agents/justifications/ | <justification-slug> [content] |
You are creating a new justification file in the .agents/justifications/ directory.
Your Task
- Determine the slug - Use
$ARGUMENTSas the file slug (kebab-case recommended) - Gather content - Collect or generate the justification content
- Create the file - Use the create-justification script to generate the file
Usage
The script will automatically:
- Generate a unique three-word ID (e.g.,
swift-emerald-river) - Create frontmatter with current date and formatted title
- Save the file as
{id}-{slug}.mdin.agents/justifications/
Creating the File
Option 1: Direct Content
If you have the content ready, run:
pnpm exec tsx scripts/create-justification.ts "$ARGUMENTS" "Your justification content here"
Option 2: Multi-line Content (Heredoc)
For multi-line content, use heredoc:
pnpm exec tsx scripts/create-justification.ts "$ARGUMENTS" << HEREDOC
Your multi-line
justification content
goes here
HEREDOC
Option 3: Pipe Content
You can also pipe content:
echo "Your content" | pnpm exec tsx scripts/create-justification.ts "$ARGUMENTS"
File Format
The created file will have:
---
date: 2026-01-13
title: Justification Title
---
Your content here
The title is automatically formatted from the slug (e.g., architecture-decision → Architecture Decision).
Guidelines
- Use descriptive slugs in kebab-case (e.g.,
tech-stack-choice,api-design-rationale) - Include clear reasoning and context for the decision
- The unique ID ensures no filename conflicts
- Files are automatically dated for organization
Begin
Create a justification file using the slug from $ARGUMENTS and appropriate content documenting the reasoning or justification.