Identifies the best local or remote repository for a task using scoped VPC checks.
npx skills add https://github.com/AndreJorgeLopes/devflow --skill resolve-repo
Please help me install this Agent Skill. Skill: resolve-repo Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/resolve-repo Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill resolve-repo
resolve-repo prevents time-wasting confusion by determining which repository a task belongs to and only cloning when the best match is not already present locally.
Use resolve-repo in a sub-agent with WORKSPACE_DIR, TICKET_ID, TICKET_TITLE, TICKET_DESCRIPTION, and TICKET_LABELS to get the most likely repository match and a ready-to-clone plan if the top candidate is remote.
High-intent search queries and answers about installing and using this skill.
To find the right git repository, this skill scores local repo names and ticket signals against lightweight metadata first. It only queries the remote VCS platform within a derived group scope if no local match is found, minimizing context bloat.
Ticket matching works by scoring local repo names, ticket IDs, titles, descriptions, and labels against lightweight package metadata. This local-first repository matching prevents time-wasting confusion by identifying the correct codebase before any remote lookup.
Yes, remote discovery is scoped to only the relevant VCS group or subgroup derived from local remotes. It queries using repo name and description without inspecting README files or source code, ensuring fast and lightweight repository resolution.
Yes, safe cloning requires user confirmation. The skill produces a ranked outcome of remote candidates and asks for explicit confirmation before cloning into the workspace, including basic setup hints for common project files.
You need to provide the TICKET_ID, TICKET_TITLE, TICKET_DESCRIPTION, and TICKET_LABELS. Passing these parameters to a sub-agent allows the skill to accurately match signals against local repos and rank remote candidates concisely.
You should avoid repository resolution via an AI agent if your task lacks clear ticket signals or if you need to inspect README files and source code during discovery, as this skill only queries repo names and descriptions to prevent context bloat.
nicolas-codemateAggregate ticket information from YouTrack, GitHub, or local files into normalized markdown.
DeL-TaiseiOzakiDetect tech stack and commands from project files to update AGENTS.md top sections.
NagyViktCreate and manage isolated git worktrees for parallel branch development.
roerohanExplore multi-repository source code and analyze library internals across public platforms.
