hai/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-05-12 07:37:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: bypass GateGuard file gates in subagents (#1710)

Browse Source
This commit is contained in:
Affaan Mustafa
2026-05-11 01:51:24 -04:00
committed by GitHub
parent f8a0c4f884
commit 7b964402ee
11 changed files with 200 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
skills/tinystruct-patterns/SKILL.md
View File

@@ -20,7 +20,7 @@ Architecture and implementation patterns for building modules with the **tinystr
## How It Works
The tinystruct framework treats any method annotated with `@Action` as a routable endpoint for both terminal and web environments. Applications are created by extending `AbstractApplication`, which provides core lifecycle hooks like `init()` and access to the request `Context`.
The tinystruct framework treats any method annotated with `@Action` as a routable endpoint for both terminal and web environments. Applications are created by extending `AbstractApplication`, which provides core lifecycle hooks like `init()` and access to the request `Context`.
Routing is handled by the `ActionRegistry`, which automatically maps path segments to method arguments and injects dependencies. For data-only services, the native `Builder` component should be used for JSON serialization to maintain a zero-dependency footprint. The framework also includes a utility in `ApplicationManager` to bootstrap the project's execution environment by generating the `bin/dispatcher` script.

2
skills/tinystruct-patterns/references/testing.md
View File

@@ -6,7 +6,7 @@ Use the testing patterns described here when writing units tests for your tinyst
## How It Works
Testing tinystruct applications requires a specific setup to ensure framework-level features like annotation processing and configuration management are active. By creating a new instance of your application and passing it a `Settings` object in the `setUp()` method, you trigger the `init()` lifecycle. This ensures all `@Action` methods are discovered and registered.
Testing tinystruct applications requires a specific setup to ensure framework-level features like annotation processing and configuration management are active. By creating a new instance of your application and passing it a `Settings` object in the `setUp()` method, you trigger the `init()` lifecycle. This ensures all `@Action` methods are discovered and registered.
Because the `ActionRegistry` is a singleton, it is critical to maintain isolation between tests by properly initializing your application state before each test execution, preventing side effects from leaking across the test suite.