br4zz4:find-in-root

Searches files and patterns across all projects in the br4zz4 workspace root.

Updated May 25, 2025
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-find-in-root-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:find-in-root
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Afind-in-root
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-find-in-root-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working in one project, files like deploy scripts, CI workflows, Makefiles, or configs often live in sibling projects. This Skill prevents wasted time asking users to paste content by searching the entire br4zz4 workspace root (~/workspace/br4zz4.tech/) directly. ## Core Features & Use Cases - Cross-project file search: Find any file by name across all br4zz4 projects using find, excluding noise directories like .git, .venv, node_modules, and __pycache__. - Pattern grep across projects: Search for code or config patterns across the whole workspace with grep -r, filtered by file type. - Known locations map: Provides a lookup table for common resources such as CI workflows (.github/workflows/), deploy scripts (scripts/deploy*.sh), supervisor configs, and Makefile targets. - Use Case: You are debugging a deployment issue in project A and suspect the deploy script lives in project B. Instead of asking the user, run the find command against ~/workspace/br4zz4.tech to locate deploy.sh instantly. ## Quick Start Search the br4zz4 workspace root to find the deploy script used by the sibling project before asking me to paste it.

Frequently Asked Questions about br4zz4:find-in-root

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

FAQPage Schema
How do I find a file across multiple projects in a workspace?▼

Use the find command against the workspace root: find ~/workspace/br4zz4.tech -name "<filename>" with exclusions for .git, .venv, node_modules, and __pycache__. This searches every project directory in one pass.

How to grep for a pattern across multiple git repositories?▼

Run grep -r with the workspace root path and filter by file extensions using --include flags, such as --include="*.sh" or --include="*.yml". Add --exclude-dir for .git, .venv, and node_modules to avoid noisy results.

Where are CI workflows and deploy scripts located in br4zz4 projects?▼

CI workflows live in <project>/.github/workflows/*.yml and deploy scripts in <project>/scripts/deploy*.sh. Supervisor configs are in <project>/supervisor/*.conf and Makefile targets in <project>/Makefile or .project/make/*.mk.

Why should search exclude .git and node_modules directories?▼

These directories contain thousands of generated or vendored files that produce irrelevant matches and slow down searches. Excluding them with -not -path or --exclude-dir keeps results focused on actual project source files.

When should I search the workspace root instead of asking the user for a file?▼

Search first whenever you need a file, script, config, or workflow that may belong to another project, or when investigating bugs that cross project boundaries. Only ask the user after the workspace search returns no results.