the signals and their derived score are provisional and subject to change.
validate manually before sharing.
58b05baab44cd5acfd5961a9379572c74a202392---
name: fix
description: Debug and fix any non-trivial issue end-to-end, OR triage a GitHub bug issue read-only. Default (`/fix [issue]`) = systematic debugging → fix → PR. `--investigate` = read-only bug triage that posts a structured investigation as a GitHub issue comment (interactive). `--investigate --auto` = the same, fully autonomous (no questions). Use anytime you need to fix a bug, or to investigate/triage one without fixing it.
argument-hint: [issue-number-or-description] [--investigate] [-----
name: save-plan-to-github
description: Post a plan or investigation block as a comment on a GitHub issue. Internal helper invoked by the investigate mode of feat / fix — not meant to be run on its own. The domain-specific template lives in the calling skill.
disable-model-invocation: true
---
Mechanics for posting an investigate block (plan or bug investigation) to a GitHub issue. The calling skill supplies the **template**; this covers the _how_, identical across feat / fix.
- Post as a **new issue---
name: document
description: best practices to write good documentation
---
Follow this guide to write proper documentation every time [write-documentation.md](./references/write-documentation.md)
---
name: open-pr
description: MANDATORY skill for ALL pull requests. Must be used EVERY TIME before creating any pull request. No exceptions.
---
# Generating Pull Requests
## Mandatory Process
**`--auto`** (caller runs autonomously): skip step 0 sign-off and any push/PR approval wait — proceed directly. Still fix push-hook errors, still `--draft`.
0. **ALWAYS** ensure the change was verified before opening the PR. For logic changes this means `./gradlew assembleDebug` compiles and `./gradlew lint` s---
name: feat
description: Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with `--investigate`. Add `--auto` to run unattended (never asks; build stops at a draft PR). Use anytime you need to build a feature, or to plan one ahead without writing code.
argument-hint: [issue-number-or-description] [--investigate] [--auto]
disable-model-invocation: true
---
Full feature lifecycle orchestrator. One flow of phases; the mode only changes how a few pha---
name: understand-project
description: Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface. Internal helper invoked by feat / fix (both modes) — not meant to be run on its own.
disable-model-invocation: true
---
Ground every plan and implementation in code that already exists. A plan that says "follows the same pattern as `src/itkach/aard2/lookup/LookupFragment.java`" beats one describing an abstraction in the---
name: writing-great-skills
description: Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
disable-model-invocation: true
---
A skill exists to wrangle determinism out of a stochastic system. **Predictability** — the agent taking the same _process_ every run, not producing the same output — is the root virtue; every lever below serves it.
**Bold terms** are defined in [`GLOSSARY.md`](GLOSSARY.md); look them up there for the full meaning.
---
name: investigate-contract
description: Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes. Internal helper invoked by the investigate mode of feat / fix — not meant to be run on its own.
disable-model-invocation: true
---
Applies whenever a skill runs with `--investigate`. The domain-specific output (a plan, or a bug triage) and any labeling live in the calling skill; this is the shared contract.
## Read-only (enforce yourself)
Investigate mode is **strictly re---
name: grill-me
description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
---
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.---
name: branch-check
description: Ensure you're on a correct working branch off up-to-date master before planning or editing — starting from a GitHub issue when one is in play.
disable-model-invocation: true
---
Run before anything else, before planning or editing.
1. Check the current branch (`git branch --show-current`).
2. If you are on `master`, you must branch — never edit directly on `master`. (This repo's default branch is `master`, not `main`.)
3. Ensure `master` is current first: `git pull ---
name: commit
description: MANDATORY skill for ALL commits. Must be used EVERY TIME before creating any git commit. No exceptions.
---
# Generating Commit Messages
## Mandatory Process
**BEFORE ANY git commit COMMAND:**
1. **ALWAYS** run `git diff --staged` first to see changes
2. **ALWAYS** analyze the staged changes thoroughly
3. **ALWAYS** split the code changes into atomic commits, one per coherent / cohesive change. Tests for a change should be in the same commit as the change itself. A single f# Android (Java) — working agreement
## Working principles
- **Ask if ambiguous.** Never decide silently — surface the choice and let the user pick.
- **Minimal diff.** Touch only what the task requires. No drive-by edits, no opportunistic refactors.
- **Define "done" before starting.** One line is enough — state the success condition up front.
- **Verify against latest code.** Never act on assumption — read the current file, run the check, confirm the state.
- **Minimum code.** Write what's needenone