Skip to content

Add configurable add-project shortcut - #4258

Closed
colonelpanic8 wants to merge 9 commits into
pingdotgg:mainfrom
colonelpanic8:t3code/add-project-shortcut
Closed

colonelpanic8 wants to merge 9 commits into
pingdotgg:mainfrom
colonelpanic8:t3code/add-project-shortcut

fix(web): read live palette state for shortcut

dad869d
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Jul 28, 2026 in 6s

Effect Service Conventions: No issues found

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.

The changed files add an alt+a / project.add keybinding and the associated command-palette UI logic. The touched modules (apps/web/src/components/CommandPalette.logic.ts, CommandPalette.tsx, keybinding config in packages/shared/src/keybindings.ts and packages/contracts/src/keybindings.ts, plus their tests) contain React component code, pure helper functions, and keybinding configuration/schema literals. None of these create, move, refactor, or consume an Effect service, so the Effect service conventions (namespace imports, Context.Service layout, dependency acquisition/runtime boundaries, tagged errors) do not apply. Effect subpath namespace imports already in use (effect/Array, effect/Result) are consistent with the conventions. No violations found.


🔍 Agent activity — reasoning, no tool calls

💭 Looking at the PR changes to see if there are any Effect service convention violations. The modifications touch keybindings tests, CommandPalette logic and components, and keybinding definitions for a new "project.add" command, but these are all UI and configuration layer changes that don't involve creating or refactoring Effect services. Looking at these file changes, none of them are actually Effect services—they're just pure functions, React components, and configuration values. The diff doesn't create, move, refactor, or consume an Effect service in any way that would trigger the conventions being checked, so the check defaults to failure with no findings. Since there are no findings, the response should be success with "All clear" as the result.