Installs into .claude/skills of the current project.
Are you the author of Resolving App?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wayne930242-resolving-app)
---
name: resolving-app
description: Use to resolve which of the project's managed apps a request belongs to.
---
## Resolve the app
Resolve the git root, then read `.straw-boss/apps.json`, or `.claude/straw-boss/apps.json` when the first is absent.
An unreadable file, invalid JSON, or an `apps` entry missing `name`, `dir`, or `match` is a configuration error: report that file and the problem, and route nothing from it.
Field meanings come from the [apps configuration schema](../../../skills/init/references/apps-config-schema.md#field-reference).
- **No configuration:** use the repo root as an implicit app when it contains one codebase. Derive its name from the manifest or directory name. With several plausible apps, ask which directory the request targets.
- **One active app:** use it unless the request is explicitly outside that app.
- **Several apps:** match the request against every entry's `name` and `match`. Return each app touched; clarify an ambiguous match.
- **Legacy entry:** apply `redirectTo` for new work and surface its `note`. An audit of existing legacy code stays in that checkout; a user-confirmed compatibility fix can also stay there.
- **External or unmanaged work:** return that classification to the caller.
## Return
Return the app names, absolute directories, config source, and applicable `crossAppSkills` pointers.
App ownership alone establishes no dependency order.
The caller uses [boss-say](../boss-say/SKILL.md#plan-and-schedule) for work needing a plan; this skill only resolves targets.
**Complete when:** the caller has unambiguous targets or a specific unresolved routing question.
