setup-project

Generate tool-specific HOTL adapter and governance files for code assistants.

25|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/yimwoo/hotl-plugin --skill setup-project-yimwoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-project
Source: https://github.com/yimwoo/hotl-plugin/tree/main/skills/setup-project
Command: npx skills add https://github.com/yimwoo/hotl-plugin --skill setup-project-yimwoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Setup Project skill streamlines HOTL integration by generating essential adapter files aligned with team tooling, ensuring consistent guardrails across code assistants.

Core Features & Use Cases

  • Generates per-tool configuration files (e.g., AGENTS.md for Codex, CLAUDE.md for Claude Code, .clinerules for Cline, .cursor/rules/hotl.md for Cursor, and GitHub Copilot instructions) based on selected tools.
  • Ensures files are placed at the project root and references HOTL operating principles, risk guidelines, and human-review requirements.
  • Use Case: A new codebase adopts HOTL and runs setup-project to auto-create governance files for selected tools, accelerating safe automation adoption.

Quick Start

Run the setup-project skill at the project root and answer the tool prompts to generate tool-specific adapters and governance files.

Frequently Asked Questions about setup-project

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

FAQPage Schema
How do I generate HOTL guardrail files for Claude Code and Cursor?▼

To generate HOTL guardrail files, run the setup-project skill at your project root and select your tools. It auto-creates root-level adapters like CLAUDE.md and .cursor/rules/hotl.md to enforce consistent guardrails across code assistants.

What is an HOTL adapter file and when do I need it for my codebase?▼

An HOTL adapter file is a root-level governance configuration that references human-on-the-loop operating principles and risk guidelines. You need it when adopting HOTL to ensure code assistants require human review before applying automated changes.

Can I use one setup process to configure Codex, Cline, and GitHub Copilot at the same time?▼

Yes, you can configure multiple assistants simultaneously. The setup-project skill validates your tool selections and generates the appropriate configuration files, including AGENTS.md for Codex, .clinerules for Cline, and copilot-instructions for GitHub Copilot.

What's the best way to ensure my project has the required SKILL.md file for HOTL automation?▼

The best way to ensure required SKILL.md presence is to run the setup-project skill. It validates the required SKILL.md file and checks your tool selections before generating the appropriate governance adapters for your chosen code assistants.

Does setup-project support generating copilot-instructions for GitHub Copilot?▼

Yes, setup-project supports generating copilot-instructions for GitHub Copilot. By selecting GitHub Copilot during the tool prompts, the skill automatically generates the appropriate root-level adapter and governance files for your project.

Why does my automated code assistant bypass human review requirements in my repository?▼

Your assistant bypasses human review because the project lacks proper HOTL governance files. Running setup-project generates necessary adapters like AGENTS.md or CLAUDE.md that explicitly reference HOTL operating principles and enforce human-review requirements.