Computer Use
D 55 completed
Other
unknown / swift · small
100
Files
8,910
LOC
0
Frameworks
5
Languages
Pipeline State
completedRun ID
#1544756Phase
doneProgress
0%Started
2026-04-16 22:53:51Finished
2026-04-16 22:53:51LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
37.22Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:36Deduplication group #47380
Member of a group with 1,432 similar repo(s) — canonical #1436887 view group →
Repobility · severity-and-effort ranking · https://repobility.com
🧪 Code Distillation
Browse all specs →AI Prompt
Create a command-line tool for macOS that allows desktop control from the terminal. I need functionality to take screenshots (including options like `capture-excluding` or `capture-region`), simulate mouse and keyboard inputs (like moving the mouse, clicking, typing text, or sending key combinations), and manage windows. It should also support session management, allowing me to start a session, grant access to specific apps, and perform orchestrated actions like clicking or batching multiple commands while enforcing safety guards. Please ensure all outputs are JSON to stdout.
swift macos cli automation desktop-control command-line scripting input screenshot
Generated by gemma4:latest
Catalog Information
Create a command-line tool for macOS that allows desktop control from the terminal. I need functionality to take screenshots (including options like capture-excluding or capture-region), simulate mouse and keyboard inputs (like moving the mouse, clicking, typing text, or sending key combinations), and manage windows. It should also support session management, allowing me to start a session, grant access to specific apps, and perform orchestrated actions like clicking or batching multiple com
Tags
swift macos cli automation desktop-control command-line scripting input screenshot
Quality Score
D
55.3/100
Structure
49
Code Quality
63
Documentation
38
Testing
15
Practices
78
Security
100
Dependencies
80
Strengths
- CI/CD pipeline configured (github_actions)
- Consistent naming conventions (PascalCase)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- 1 files with critical complexity need refactoring
- 1432 duplicate lines detected — consider DRY refactoring
- 1 'god files' with >500 LOC need decomposition
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Symbols
property1,382
method499
struct123
enum53
class23
function4
extension2
Embed Badge
Add to your README:
