Claude Skills by kbarendrecht

github.com/kbarendrecht

8 skillsA× 7B× 10 installs11 views

Architecture Health CheckARead-only architecture health check for orchd — find where many individually reasonable changes have gradually degraded the architecture (responsibility accumulation, workflow fragmentation, conditional sprawl, boundary violations, unclear state ownership, incremental duplication, over-stretched abstractions). Produces a prioritized, evidence-backed report and modifies no code. Use for a periodic review, or after a subsystem has grown a lot. Optionally pass a path, subsystem, or git range to ...developmentrustgoVotes: 0GitHub stars: 7
Domain Consistency ReviewARead-only product & domain consistency review for orchd — reconstruct the domain model from the implementation, then check whether the domain logic is internally coherent. Finds contradictions, unclear state ownership, impossible states, duplicated business rules, and rules enforced in one place but bypassed in another — especially across the SPA / daemon / persistence / GitHub / background-poller boundaries. Produces inferred domain rules plus evidence-backed inconsistencies and modifies no ...developmentgorefactoringVotes: 0GitHub stars: 7
Fix PrAGet a pull request green. Take its base branch in, fix the red checks, amend, push, and watch until the checks settle. Mechanical only: never comments, never resolves a thread, never merges the PR itself. Use when somebody asks you to fix, rebase or unbreak a PR's CI, or when the orchestrator hands you a fix run.developmentgotestingVotes: 0GitHub stars: 7
GreenAGet a PR green. Rebase it on its base branch, fix the easy red, ask about the rest, amend into the commit that owns the change, force-push, and watch CI until it passes. Use when a PR is red or has fallen behind, and never for review threads, which are somebody's words rather than a failing check.developmenttestinggitVotes: 0GitHub stars: 7
Handle ReviewAWork through a pull request's review threads in a pane — judge each one, apply what is right, ask about the rest, draft replies and post only on an explicit go. Use when somebody asks you to resolve, handle or answer the review feedback on a PR.developmentgobashVotes: 0GitHub stars: 7
OrchAHow to reach the orchestrator you are running inside — ask the human a blocking question, start or end another session, list the sessions and where they run, or start one of the workspace's declared processes. Use whenever you need a decision from the person watching, want a second session to work in parallel, or need to know what else is running before touching a branch or a worktree.developmentbashgitVotes: 0GitHub stars: 7
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
ReviewBAnswer a pull request's review threads end to end with a human deciding in the orchestrator's overlay — read the threads and propose options, make the changes they pick, then post the replies. Use when the orchestrator starts a review session, or when somebody asks you to work a PR's review feedback with the overlay driving.developmentgobashVotes: 0GitHub stars: 7
StoryAFile tracker stories for review threads a human already approved — search for an existing one first, create at most one per entry, and report each id and URL back. Places records only: never rewrites the approved text, never edits the worktree, never posts. Use when the orchestrator starts a story pass.developmentgoVotes: 0GitHub stars: 7