git-final-pass

Pre-PR quality checklist encoding recurring review feedback. Run before creating a PR to catch common mistakes. Covers: error handling, naming, resource cleanup, test coverage, documentation, commit hygiene, and language-specific gotchas. Use when code is "done" and about to be PR'd.

Ir a la instalación

Repositorio: robert-chiniquy/dotfiles
Última actividad en el origen: 26 de julio de 2026 a las 21:20
Idioma detectado de SKILL.md: inglés
Estrellas: 3
Forks: 1

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/robert-chiniquy/dotfiles --skill git-final-pass

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

find-delegation-pebbles

Sweep open issue trackers, TODOs, active branches, and source evidence to find narrowly scoped, independent, verifiable tasks suitable for remote agents or parallel delegation. Use when asked to find pebbles, small delegatable work, fire-and-forget candidates, backlog slices, ready items, or pool/task combinations.

2026-07-29

readiness-scorecard

Write a scorecard — a dark, skimmable one-screen readout of the current situation in the user's work, rendered as a terminal (TUI) artifact by the `scorecard` binary from a structured markdown file. Use ONLY when the user explicitly asks for a scorecard (or a "readiness card" / "go/no-go card" / "coverage snapshot card"). A plain "status", "status?", or other status/situation question gets a prose answer, never this skill. NOT a web page — output is the dark TUI. Preserves older scorecards by datestamp. Triggers on: scorecard, readiness card, go/no-go card, coverage snapshot card.

2026-07-27

bar-chart-comparison

Present comparisons as narrow ASCII bar charts in the terminal. Use when user asks to compare items, metrics, counts, or coverage between things.

2026-07-26

Ver todos los de este repositorio

name	git-final-pass
disable-model-invocation	true
description	Pre-PR quality checklist encoding recurring review feedback. Run before creating a PR to catch common mistakes. Covers: error handling, naming, resource cleanup, test coverage, documentation, commit hygiene, and language-specific gotchas. Use when code is "done" and about to be PR'd.
allowed-tools	["Read","Grep","Glob","Bash"]

Final Pass

Run this checklist before creating a PR. Every item is a mistake that has actually happened.

Process

Identify changed files: git diff --name-only HEAD~1 or git diff --name-only main
Run each check category against changed files only
Produce a pass/fail table
Fix failures before proceeding to PR

Checks

Error Handling

Check	What to look for
Unchecked errors	Go: `err` assigned but not checked. TS: `.catch()` missing on promises
Swallowed errors	`catch {}` or `if err != nil { return nil }` with no logging
Error message quality	Does the error say what went wrong AND what was being attempted?

Check	What to look for
Abbreviation	No abbreviations except universally understood (id, url, http, db)
Boolean naming	Booleans should read as questions: `isReady`, `hasPermission`, `canRetry`
Consistency	Same concept uses same name everywhere. Don't mix `user`/`account`/`principal`
Exported names	Go: exported names should not stutter (`user.UserName` -> `user.Name`)

Check	What to look for
Open/close pairing	Every open (file, connection, channel) has a corresponding close
Defer placement	Go: `defer` immediately after successful open, not after error check
Context cancellation	Go: `context.WithCancel` always has `defer cancel()`
Goroutine lifetime	Every goroutine has a clear termination condition

Check	What to look for
New code has tests	Every new function/method has at least one test
Tests have failure hypothesis	Each test name describes what breaks: `TestRejectsExpiredToken`
No weakened tests	Tests weren't modified to make them pass (weaker assertions, removed cases)
Edge cases	Empty input, nil/null, zero values, boundary conditions
Error paths tested	Not just happy path — test what happens when things fail

Check	What to look for
Public API documented	Exported functions/types have doc comments
Changed behavior noted	If behavior changed, docs updated to match
README current	If user-facing changes, README reflects them
No stale comments	Comments near changed code still accurate

Check	What to look for
No unrelated changes	Every file in the diff relates to the PR's purpose
No debug artifacts	No `console.log`, `fmt.Println`, `print()` left in
No commented-out code	Dead code should be deleted, not commented
No TODOs without tickets	New TODOs reference a tracking number or explain why they exist
No secrets	No API keys, tokens, passwords, or internal URLs
.gitignore current	Generated files (binaries, build output) are ignored

git-final-pass

Opciones de instalación

Revisa los archivos de origen

Final Pass

Process

Checks

Error Handling

Final Pass

Process

Checks

Error Handling

Naming

Resource Cleanup

Tests

Documentation

Commit Hygiene

Language-Specific: Go

Language-Specific: TypeScript

Common Mistakes

Output

Check	What to look for
Nil pointer	Interface values checked for nil before method calls
Slice nil vs empty	`nil` slice and `[]T{}` behave differently in JSON marshaling
Map initialization	Maps must be initialized before write (`make(map[K]V)`)
Race conditions	Shared state across goroutines protected by mutex or channel
Import organization	stdlib, external, internal — separated by blank lines

Check	What to look for
Any types	No `any` unless genuinely unavoidable (document why)
Null handling	Optional chaining (`?.`) or explicit null checks, not `!` assertions
Async error handling	Every `async` function has error handling or propagates correctly
Type narrowing	Union types narrowed before use, not cast with `as`

git-final-pass

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Final Pass

Process

Checks

Error Handling

Final Pass

Process

Checks

Error Handling

Naming

Resource Cleanup

Tests

Documentation

Commit Hygiene

Language-Specific: Go

Language-Specific: TypeScript

Common Mistakes

Output