try

Generates a read-only manual testing guide for recently implemented features or fixes.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill try-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: try
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/try
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill try-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an AI agent implements a feature, fix, or rollback, developers often struggle to know exactly how to manually verify the change. This Skill reads the project spec and commands, then produces a concrete step-by-step walkthrough telling you what to start, where to click, what to expect, and what failure signs to watch for. ## Core Features & Use Cases - Manual Review Guides: Produces structured Start, Open, Do, Expect, and Watch For sections based on the active Blueprint feature spec. - Project-Aware Commands: Matches the guide to your project type (web app, API, CLI, library, or hybrid) using commands defined in AGENTS.md. - Read-Only Safety: Never edits files, installs dependencies, commits, or runs destructive commands while generating the guide. - Use Case: After running /implement on a new admin dashboard route, invoke /try to get exact instructions like which dev server to start, which URL to open, which buttons to click, and which console errors indicate a problem. ## Quick Start Ask the agent to run /try after completing a feature to receive a step-by-step manual verification guide for the change.

Frequently Asked Questions about try

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

FAQPage Schema
How do I manually test a feature after an AI agent implements it?▼

Invoke the /try command after /implement or /complete. The skill reads the active feature spec and project commands, then outputs a numbered guide covering what to start, which route to open, what to click, expected results, and warning signs.

What is the difference between /check and /try in a Blueprint workflow?▼

/check verifies behavior from the agent side through automated inspection, while /try produces a human-facing manual walkthrough. Use /try when you want to personally click through the change and confirm it works.

Can /try run the app or execute commands for me?▼

No, the skill is strictly read-only and does not run the app, edit files, install dependencies, or execute destructive commands. It only tells you which commands to run yourself unless you explicitly ask the agent to try it for you.

What happens if there is no active feature when I run /try?▼

The skill falls back to the most recent archived feature, fix, or rollback under blueprint/history and tells you which archive it used. If nothing useful exists, it asks what change you want to try instead of guessing.

Does the /try guide work for APIs and CLI tools, not just web apps?▼

Yes, the skill matches the project type from AGENTS.md. For APIs it gives the endpoint, method, and expected response shape; for CLIs it gives exact commands, arguments, and expected output.