ptp-config

Edits ptp layered JSON config files through a guided target, parameter, and value selection flow.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-config-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-config
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-config
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-config-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hand-editing ptp's layered JSON configuration files risks malformed JSON, wrong-shape values, and clobbered keys. This Skill replaces manual editing with a guided, schema-aware flow that validates every input and performs a safe merge-write preserving all existing keys. ## Core Features & Use Cases - Guided three-step flow: Select a config layer (global, project, or workspace), pick a parameter from a 24-entry registry, then choose or enter a validated value. - Safe merge-write: Refuses to modify malformed or wrong-shape files, creates missing files and directories, and preserves every existing key including the deploy block. - Schema-aware validation: Enforces enum values, integer ranges, boolean literals, and string rules (e.g. repository-relative telemetry roots, GitHub login format for backlog owners). - Use Case: A user wants Codex reviews to be mandatory rather than optional. They run the config command, select the project layer, choose "Use Codex for review", pick required, and the Skill writes exactly that key without touching anything else. ## Quick Start Ask the assistant to open the ptp config editor and change a setting such as the Codex review mode or telemetry retention in the project config file.

Frequently Asked Questions about ptp-config

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

FAQPage Schema
How do I change ptp configuration settings without editing JSON by hand?▼

Run the ptp config command, which walks you through selecting a config layer (global, project, or workspace), picking a parameter from a labeled menu, and choosing a validated value. It then performs a safe merge-write that preserves all existing keys.

What settings can the ptp config editor change?▼

The registry holds 24 parameters covering Codex review mode, model, and reasoning effort, review-loop iterations and severity thresholds, telemetry mode, root, port, and retention, parallel execution, artifact word budgets, backlog project mapping, and TDD enforcement.

What happens if my ptp config.json file is malformed?▼

The command stops and reports the parse failure without modifying the file. It also stops if the JSON root is not an object or if a parameter's parent key exists but is not an object, since merging would clobber data.

What is the difference between global, project, and workspace ptp config layers?▼

Global lives at ~/.claude/ptp/config.json, project at the git repository root's .claude/ptp/config.json, and workspace at the workspace root resolved by the ptp-workspace skill. The workspace option appears only when its path differs from the project path.

Why does the ptp config editor reject absolute paths for telemetry.root?▼

The telemetry root must be a repository-relative path strictly below the repository root, because the telemetry store writes its own .gitignore and .gitattributes into that root. Absolute paths, parent-directory segments, and the repository root itself are rejected and re-prompted.