with one click
forge2-chiru
forge2-chiru contains 15 collected skills from chiruu12, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Turn a feature or sprint goal into an ordered backlog of small, testable issues with dependencies. Hermes uses this to write sprints/sprint-0N.md.
Hermes's format for handing ONE scoped, testable issue to OpenClaw in
The non-negotiable architecture rules Hermes enforces when assigning and reviewing work — Laravel layering, tenancy, auth, and the human-merge gate.
Post GitHub Actions CI results to the
Define PulseDesk's domain entities and relationships before assigning model work, so the data model stays coherent. Source of truth is ARCHITECTURE.md.
Recipe for a new Eloquent model in PulseDesk — model + migration + factory + seeder + tenant trait. Use when introducing a domain entity.
Git discipline for the agent loop — branch per issue, small incremental commits, open a PR, never merge. Keeps the timeline genuine and reviewable.
Recipe for adding a REST endpoint to PulseDesk — route, controller, FormRequest, policy, JsonResource, and feature test. Use for every new API action.
PulseDesk's Pest feature-test pattern — auth setup, happy path, role denial, and the mandatory cross-tenant 404. Every endpoint PR includes these.
OpenClaw's structured status report for the
Reviewer agent's triage of an opened PulseDesk PR — assess scope, tenant-safety, correctness, and tests, then post a verdict to Slack and comment on the PR. Routed via EastRouter. Never merges.
Build a React 19 + Tailwind feature from a mock, feature-first, wired to the Laravel JSON API. The mock is look-only; adapt structure/state/validation to the stack.
Install and wire Laravel Sanctum token auth for PulseDesk — install:api, register/login/logout/me, roles, and role middleware. The auth foundation.
The PulseDesk multi-tenancy pattern — BelongsToOrganization trait, global scope, SetTenantContext middleware, and the cross-tenant 404. Apply to every tenant-owned model. This is the security-gated criterion.
The shared PulseDesk vocabulary used identically across backend, React, and Slack, so agents and humans mean the same thing.