docs: added Cursor Dependency Sweeper example #222

[Mahizhan-S]

Summary

This PR adds a Cursor-specific Dependency Sweeper example by adapting the existing Opencode implementation to Cursor Automations and Agent workflows. The new example follows the structure and conventions used by the existing Cursor documentation while preserving the safety and verification guidance from the Dependency Sweeper pattern.

Changes

Added

• examples/cursor/dependency-sweeper.md

  • Introduces a complete Cursor example for the Dependency Sweeper pattern.
  • Includes a report-only automation prompt for the initial rollout.
  • Documents the progression from reporting to patch-only automation.
  • Describes the use of isolated worktrees for each fix attempt using npx @cobusgreyling/loop-worktree.
  • Includes verifier approval before any merge proposal.
  • Documents a human gate for major version upgrades.
  • Covers denylist usage, safety guidance, and an example dependency-sweeper-state.md.
  • References the related pattern, safety documentation, story, and primitives matrix.

Updated

• examples/cursor/README.md

  • Added the Dependency Sweeper example to the Cursor examples table.

• examples/README.md

  • Updated the Pattern Coverage table to include the new Cursor Dependency Sweeper example.

Notes

The implementation intentionally mirrors the structure of the existing Opencode Dependency Sweeper example while adapting the scheduling and execution model for Cursor Automations and Agent workflows. It also follows the established style used by the existing Cursor examples to maintain consistency across the documentation.

Validation

• Verified documentation links and repository consistency using:

  npx @cobusgreyling/loop-audit . --suggest

• Audit completed successfully with no reported issues or broken links.

• Limited the changes to the three files required by the issue.

• Verified there are no whitespace or formatting issues using:

[github-actions]

Thanks @Mahizhan-S for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone.

What happens next

• Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
• good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

• Contributor quickstart + open issues
• Good first issue backlog

— loop-engineering maintainers