project-triage

Detect Frappe project type, installed apps, version, and tooling before making code changes.

62|23|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/lubusIN/frappe-skills --skill project-triage-lubusin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-triage
Source: https://github.com/lubusIN/frappe-skills/tree/main/project-triage
Command: npx skills add https://github.com/lubusIN/frappe-skills --skill project-triage-lubusin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When opening an unfamiliar Frappe or ERPNext codebase, developers often run commands against the wrong site, assume apps are installed that are not, or modify DocTypes without developer mode enabled. This Skill provides a structured triage procedure to understand the project environment before touching any code. ## Core Features & Use Cases - Project Structure Detection: Identifies whether the codebase is a Bench installation, a Frappe Manager Docker site, a standalone app, or an app module based on directory patterns like apps/, sites/, and docker-compose.yml. - Environment Inspection: Lists installed apps, checks the Frappe version, verifies developer mode, and catalogs available tooling such as Cypress, CI workflows, and JS build tooling. - Skill Routing: Produces a structured triage report that routes follow-up work to the appropriate skill such as doctype-development, api-development, or testing. - Use Case: You clone a client's Frappe repository and need to add a custom DocType. Run triage first to confirm the bench root, verify ERPNext is installed, check the Frappe version, and confirm developer mode is enabled before making schema changes. ## Quick Start Analyze this Frappe project and report its type, installed apps, version, developer mode status, and available tooling.

Frequently Asked Questions about project-triage

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

FAQPage Schema
How do I check which apps are installed on a Frappe site?▼

Run bench --site <site> list-apps from the bench root to see all installed apps. You can also inspect the apps/ directory to see which app repositories are present in the environment.

How to find the Frappe version of a project?▼

Run bench version from the bench root, or open a console with bench --site <site> console and print frappe.__version__. Knowing the version matters because APIs and patterns differ significantly across major releases.

What is the difference between Bench and Frappe Manager environments?▼

A Bench installation has apps/ and sites/ directories with a Procfile, while Frappe Manager uses Docker with a docker-compose.yml file. In Frappe Manager you enter the environment with fm shell <site> instead of running bench commands directly.

Why does bench command not found happen in a Frappe project?▼

This happens when you are not inside a bench environment or the virtualenv is not activated. If the project uses Frappe Manager, run fm shell <site> first; otherwise navigate to the bench root where the apps/ directory exists.

When should I enable developer mode in Frappe?▼

Developer mode is required before making DocType schema changes, since without it modifications to DocTypes are not persisted as JSON files. Check it via frappe.conf.developer_mode in the site console before starting schema work.