Invoke local-rules skill.
Let code speak for itself. Choose clear names, extract well-named functions, and use types to document intent instead of comments.
Group files by domain or feature (e.g. auth/, billing/), not by technical role (e.g. utils/, helpers/).
Only export symbols that are imported by another module. Default to unexported.
Give each React component its own file. Colocate small helpers and types in the same file if they serve only that component.
Scaffold new modules, components, or packages with the project's CLI generators. Check AI docs for available commands before writing boilerplate by hand.
Install dependencies through the package manager's add command so lockfiles and manifests stay in sync.

Más de este repositorio

mismo repositorio

review-pr

p2kmgcl/chachi-shell

Reviews a GitHub PR and creates a pending review with editorially gated inline/body findings. Use when the user asks to review a PR or create a draft GitHub review.

2026-07-016

local-rules

p2kmgcl/chachi-shell

Load machine-local rule overrides for a given skill from the shared ~/.agents skills directory.

2026-06-026

commit

p2kmgcl/chachi-shell

Create one or more atomic commits from current changes, grouping by logical unit

2026-06-026

create-ticket

p2kmgcl/chachi-shell

Create a JIRA ticket interactively — gathers requirements through conversation, proposes the ticket, and creates it after approval

2026-06-026

grill-with-docs

p2kmgcl/chachi-shell

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

2026-06-026

handoff

p2kmgcl/chachi-shell

Compact the current conversation into a handoff document for another agent to pick up.

2026-06-026

name	write-code
description	Coding standards to follow when writing or modifying code in any project

Invoke local-rules skill.
Let code speak for itself. Choose clear names, extract well-named functions, and use types to document intent instead of comments.
Group files by domain or feature (e.g. auth/, billing/), not by technical role (e.g. utils/, helpers/).
Only export symbols that are imported by another module. Default to unexported.
Give each React component its own file. Colocate small helpers and types in the same file if they serve only that component.
Scaffold new modules, components, or packages with the project's CLI generators. Check AI docs for available commands before writing boilerplate by hand.
Install dependencies through the package manager's add command so lockfiles and manifests stay in sync.