toolkit-cli

Document how aitk CLI commands overwrite, merge, or ignore project configuration files.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill toolkit-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toolkit-cli
Source: https://github.com/erclx/aitk/tree/main/claude/skills/toolkit-cli
Command: npx skills add https://github.com/erclx/aitk --skill toolkit-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents accidental data loss by providing a clear, authoritative reference on how aitk commands interact with your project files, ensuring you know exactly what will be overwritten, merged, or ignored before you execute a command.

Core Features & Use Cases

  • Impact Analysis: Provides a detailed contract of how sync commands affect golden configs, dictionary seeds, and standards.
  • Safety Guardrails: Offers clear guidance on which files are user-owned versus tool-managed, helping you avoid destructive operations.
  • Use Case: Before running a global tooling update, consult this skill to confirm whether your local eslint configurations will be preserved or overwritten by the toolkit's golden standards.

Quick Start

Ask the toolkit-cli skill to explain the overwrite contract for the aitk tooling sync command before you run it in your terminal.

Frequently Asked Questions about toolkit-cli

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

FAQPage Schema
How do I safely sync project configuration files without overwriting local changes?

To safely sync project configuration files, consult the toolkit-cli reference to analyze the overwrite contract for aitk commands. It clarifies file-specific merge and overwrite behaviors, ensuring your local configuration changes are preserved during global tooling synchronization operations.

What is the difference between user-owned seeds and tool-managed golden configurations?

User-owned seeds are local configuration files you maintain, while tool-managed golden configurations are standardized standards enforced by the toolkit. The distinction ensures governance rules and documentation sync safely without accidental data loss during project updates.

Will running an aitk sync command overwrite my local eslint configuration?

Running an aitk sync command may overwrite local eslint configurations depending on the file-specific contract. Check the impact analysis provided by the toolkit-cli to confirm whether your specific configuration files are user-owned or managed by golden standards.

How does aitk tooling handle merge behaviors for governance rules and documentation?

Aitk tooling handles governance rules and documentation by applying file-specific merge behaviors during synchronization. The toolkit-cli reference provides a detailed contract explaining exactly which project-level standards are merged, overwritten, or ignored before execution.

When should I check the operational impact of CLI commands on project standards?

You should check the operational impact of CLI commands on project standards before executing any global tooling update or synchronization. This prevents destructive operations by confirming which files are tool-managed and avoiding accidental loss of local configuration seeds.

Can I use toolkit-cli to analyze file operations before running terminal commands?

Yes, you can use toolkit-cli to analyze file operations before running terminal commands. Ask the skill to explain the overwrite contract for the aitk tooling sync command to receive detailed guidance on how your project state will be affected.