[BUG] apm prune does not delete packages from apm_modules
Open
Nobody has claimed this yet.
area/cli
area/lockfile
status/accepted
theme/portability
triage/recommended
type/bug
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 362
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 132
Description
I installed a skill (using "apm install microsoft/skills/.github/plugins/azure-skills/skills/azure-ai") without any problem.
Then I removed the row from apm.yml and launched
- apm install --> skills has been removed from .agents/skills
- apm prune --> package has NOT been remove from apm_modules even if on CLI has been writen
[>] Analyzing installed packages vs apm.yml...
[+] No orphaned packages found. apm_modules/ is clea
Expected behavior
Package should be deleted from apm_modules folder.
Environment (please complete the following information):
- OS: Windows 11
- Python Version: 3.13.15
- APM Version: 0.31.0
- VSCode Version: 1.138.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows 11 case with the apm.yml entry removed, then run apm prune and inspect the related handling of apm_modules/ and .agents/skills. Compare the installed package state with apm.yml and confirm that the orphaned package is removed from apm_modules/ and the CLI output reports it accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100