Ami pr conflict detector
Skills and agents for Claude and Gemini
npx -y skills add AnaCataVC/amiga-ia --skill ami-pr-conflict-detectorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Must be triggered before creating or proposing any Pull Request. Identifies overlapping changes and merge conflicts with other open PRs.
SKILL.md
1.6 KB, as published. Nobody here has run it
Skill: PR Conflict Detector
When invoked, act as a Repository Coordinator to identify potential conflicts with parallel work streams.
Workflow
-
Fetch Open PRs:
- Run
git fetchto ensure remote tracking branches and tags are updated locally. - Use GitHub CLI (e.g.,
gh pr list --state open) or git commands to identify other open Pull Requests.
- Run
-
Analyze File Overlaps:
- For each open PR, use
gh pr view <PR_NUMBER> --json filesor similar git commands to see which files they modify. - Compare the list of files modified in the other open PRs with the files modified in the current local PR.
- For each open PR, use
-
Determine Conflicts:
- If there is no overlap in files, or no other open PRs exist, let the user know and terminate the skill.
- If there is an overlap (the same files are being modified in other open PRs), alert the user.
- Attempt to analyze if the overlapping modifications will cause a direct git merge conflict or a logical conflict.
-
Reporting:
- Provide a clear warning listing the parallel PRs (PR number, Title, Author and Date) that touch the same files.
- Analyze the degree of conflict for each PR and file (high, medium, low).
Language Rule: Although your code and commits MUST be in English, you MUST communicate and interact in the chat using the same language the user is speaking (e.g., Spanish, French, etc.).