Reusable, repository-focused workflows for coding assistants. Each skill is self-contained and combines a focused SKILL.md entry point with the references, scripts, and evaluations needed for its workflow.

Review diffs for actionable bugs and regressions using targeted searches, focused reads, and verified findings. Uses Uber's Go Style Guide, Google's C++ Style Guide, and Roblox's Lua Style Guide for language-standard compliance, with version-aware correctness and lifecycle checks. Reviews are read-only unless changes are requested.

Build a defensible mental model of an unfamiliar repository before making changes. The workflow covers:

• The project's critical vocabulary and how its concepts relate
• Architecture and important data flows
• Database schemas or key layouts for stateful services
• API maps for services and public interface maps for libraries
• Orthogonality analysis and a guided interview to test understanding

The generated report is saved as <repo-name>.md in the current working directory unless another location is requested.

Write factual, reviewable pull request titles and summaries and Git commit messages. The workflow derives the change story from repository evidence, explains cause and effect, follows local templates, and keeps commit subjects and bodies within conventional length limits.

Implement changes as if they were written by the repository's maintainers. The workflow emphasizes:

• Reading the relevant layers and a sibling feature before implementation
• Reusing the repository's vocabulary, helpers, and conventions
• Designing orthogonal package or module boundaries before adding files
• Designing storage, service, and API layers in dependency order
• Keeping public contracts and exported surface area minimal
• Testing compatibility and critical behavior instead of implementation details

For bug fixes, Wise Coding follows its Issue Fixes reference workflow: reproduce the failure, identify its cause, make the smallest fix, and verify a regression test. When a PR is requested, it uses a Problem / Reproduction / Fix / Test summary.

Copy or link the complete skill directory from skills/ into the location supported by your coding assistant, then invoke the skill by name or make a request that matches its description. Keep the directory intact so relative links from SKILL.md continue to resolve.

Example requests:

Use fast-learning to help me understand this repository.

Use git-writing to draft the PR title, summary, and commit message for this change.

Use wise-coding to add this feature while following the repository's existing design.

skills/<skill-name>/
├── SKILL.md       # Purpose, trigger description, principles, and workflow
├── evals/         # Example tasks used to evaluate the skill
├── references/    # Detailed guidance loaded when relevant
└── scripts/       # Optional deterministic helpers

Not every skill needs every optional directory.

Licensed under the Apache License 2.0.