skills.rest
hcross
hcrossCOMMUNITY
Explore all skills by this author →
Website𝕏@hcrossGitHub

developer

Enforce small, verifiable code changes across multi-module projects.

3|Updated Mar 16, 2026
Search Tags:#testing#refactoring#branching#coding#best-practices#code-review#guardrails
One-click install
npx skills add https://github.com/hcross/crewrig --skill developer-hcross
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/hcross/crewrig/tree/main/.gemini/skills/developer
Command: npx skills add https://github.com/hcross/crewrig --skill developer-hcross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementation tasks often balloon into over-engineered changes. This skill provides a disciplined approach to coding work, ensuring modifications remain focused, testable, and reversible.

Core Features & Use Cases

  • Branch setup: create a fresh branch aligned with the mainline before work.
  • Read before writing: study the related code, tests, and contracts to avoid guesswork.
  • Smallest correct change: implement the minimal change that fixes the issue or adds the feature.
  • Prove it locally: run tests and validations to confirm the change works.
  • Parallelisable work: enables safe, independent tasks that can be executed concurrently.
  • Friction reporting: when issues arise, use harness-report to document frictions.

Quick Start

Open a new branch, read the surrounding code and tests, then implement the smallest correct change and prove it locally.

Frequently Asked Questions about developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep code changes small and verifiable during refactoring?▼

To keep refactoring changes small and verifiable, enforce a disciplined workflow: study existing contracts, implement the minimal correct modification, and run targeted tests to prove it works locally.

What is the best way to automate bug fixes without over-engineering?▼

Automating bug fixes without over-engineering requires enforcing minimal surface changes. You read the related code and tests first, then implement the smallest correct change that resolves the issue while maintaining testability.

How do I set up a branch workflow for parallel coding tasks?▼

Setting up a branch workflow for parallel coding tasks involves creating a fresh branch aligned with the mainline before work begins. This enables safe, independent tasks that can be executed concurrently without conflicts.

How do I document frictions when implementation tasks get blocked?▼

To document frictions when implementation tasks get blocked, use a friction reporting mechanism like harness-report. This records the specific issues encountered during the disciplined code change process.

Can I use this approach for multi-module project feature tweaks?▼

Yes, this disciplined coding approach applies to multi-module projects. It enforces branch workflows, targeted tests, and minimal surface changes to ensure feature tweaks remain focused and reversible across complex project structures.

Why should I read code before writing changes for bug fixes?▼

Reading code before writing changes for bug fixes avoids guesswork. Studying the related code, tests, and contracts ensures the smallest correct change is implemented accurately, reducing the risk of unintended side effects.

Related Skills

Explore More Software Engineering Skills→
vessuxvessux
1

using-git-worktrees

Create an isolated Git worktree workspace for feature development.

Community
Advanced
0xEdenY0xEdenY

consistency-guard

Generate dependency maps and run cross-document consistency checks.

Community
Intermediate
sambersamber
2.9k

golang-lint

Configure and run golangci-lint to analyze Go projects and interpret results.

Community
Advanced
petertrihopetertriho
3

implement

Implement minimal code changes for bug reports and tasks with validation reporting.

Community
Advanced