chore: tighten taskfile clean task

[KooshaPari]

User description

Expand the generated-cache cleanup set so the common clean task removes nested Python lint/test caches alongside existing build artifacts.

Co-authored-by: Codex noreply@openai.com

Note

Low Risk
Low risk: only broadens cache/artifact deletion in the clean task, with no runtime or production code changes; risk is limited to potentially deleting more local dev files than before.

Overview
Tightens Taskfile.yml’s clean task by expanding the set of generated directories removed during cleanup.

In addition to build artifacts, it now also removes common nested Python tooling caches like .mypy_cache, .pytest_cache, and .ruff_cache (alongside .venv, __pycache__, and *.egg-info).

^{Reviewed by Cursor Bugbot for commit 117b3ef. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Remove more Python cache files during the shared clean task

What Changed

• The shared clean task now removes MyPy cache folders in addition to the existing pytest and Ruff caches
• Cleanup still clears build output, virtual environments, package metadata, and other generated folders

Impact

✅ Cleaner local workspaces
✅ Fewer stale Python lint and test caches after cleanup
✅ Less manual cleanup before rerunning tools

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 51 minutes and 28 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 17591213-486c-41b2-b23d-13e2797504f1

📥 Commits

Reviewing files that changed from the base of the PR and between d861220 and 117b3ef.

📒 Files selected for processing (1)

• Taskfile.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/taskfile-common-tasks

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch chore/taskfile-common-tasks

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• Taskfile.yml - Clean task enhancement to include Python cache directories in cleanup

---

_{Reviewed by ling-2.6-1t-20260423:free · 489,557 tokens}

[codeant-ai]

CodeAnt AI is running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Sequence Diagram

This PR updates the shared clean task so its Python cleanup script now removes additional Python tooling caches (mypy, pytest, ruff) alongside existing virtualenv, build, and dist artifacts.

sequenceDiagram
    participant Developer
    participant TaskRunner
    participant PythonCleanup
    participant Filesystem

    Developer->>TaskRunner: Run clean task
    TaskRunner->>PythonCleanup: Execute cleanup script with project root
    PythonCleanup->>Filesystem: Delete top level cache dirs (ruff, pytest, task, rust target)
    PythonCleanup->>Filesystem: Recursively remove generated dirs and caches (venv, mypy, pytest, ruff, build, dist, egg info)
    Filesystem-->>Developer: Project workspace cleaned of generated artifacts and Python caches

Loading

---

Generated by CodeAnt AI

[codeant-ai]

CodeAnt AI finished running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI is running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Sequence Diagram

This PR expands the shared clean task so that running it now also removes nested Python tooling caches (including mypy, pytest, and ruff) in addition to existing build artifacts and virtual environments.

sequenceDiagram
    participant Developer
    participant TaskRunner
    participant CleanupScript
    participant FileSystem

    Developer->>TaskRunner: Run clean task
    TaskRunner->>CleanupScript: Execute cleanup routine
    CleanupScript->>FileSystem: Delete top level cache and build directories
    CleanupScript->>FileSystem: Recursively remove venv, tooling caches, and egg info directories
    FileSystem-->>Developer: Local workspace cleaned

Loading

---

Generated by CodeAnt AI

[codeant-ai]

CodeAnt AI finished running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn