agentleFS
Sign inStart free
CarriedWorldUniverseCarriedWorldUniverse/nexus/.agents/skills/development/SKILL.md

development

Skill0 starsChanged 34 days agoApache-2.0View on GitHub

How to implement a dispatched ticket on nexus — test-first, root-cause debugging, single-ticket discipline, verify before the PR.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use issue-campaign, contracts and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • samchonSkill

    issue-campaign

    Defines the default solo repository-wide issue campaign for typia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo Self-Review, and repeated rediscovery until a full clean round. Use for broad audits, many issue candidates, or repeated issue-to-pull-request campaigns unless the user explicitly requests parallel or multi-agent execution; do not use for one already-defined issue or an ordinary pull request.

    Also in 3 projects that use this

  • AnthropicSkill

    contracts

    Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says, which contracts have a clause, what changed between amendments, or any question that needs reading and citing across a set of contract files. The corpus must be on the local filesystem (see README).

    Also in 3 projects that use this

  • MicrosoftSkill

    pull-request

    Write concise, focused pull request descriptions for Wassette — at most three sentences on the what and why, with an explicit note on any breaking public-API change and how users adapt. Use when opening or editing a Wassette pull request.

    Also in 3 projects that use this

  • MicrosoftSkill

    typescript

    TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.

    Also in 3 projects that use this

  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 3 projects that use this

  • AnthropicSkill

    documentation

    Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.

    line 12
  2. Distinctive:

    Write one small failing test for the behaviour you want.

    line 13
  3. Distinctive:

    Run it. Watch it fail for the right reason.

    line 14
  4. Distinctive:

    Write the minimal code to pass.

    line 15
  5. Distinctive:

    Commit. Repeat for the next behaviour.

    line 17
  6. Distinctive:

    If you wrote code before the test, delete it and start from the test.

    line 18
  7. Distinctive:

    NO FIXES WITHOUT FINDING THE ROOT CAUSE.

    line 22
  8. Distinctive:

    Read the error message fully — it usually says what's wrong.

    line 23
  9. Distinctive:

    Test behaviour, not implementation detail.

    line 29
  10. Distinctive:

    Before you finish, load the security skill and load the house-style skill, and apply them.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

development

One ticket per branch, branched off the latest main. No dead code, no unrelated changes.

Test-first (the iron law)

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.

  1. Write one small failing test for the behaviour you want.
  2. Run it. Watch it fail for the right reason. (If you didn't watch it fail, you don't know it tests the right thing.)
  3. Write the minimal code to pass.
  4. Run it. Green.
  5. Commit. Repeat for the next behaviour. If you wrote code before the test, delete it and start from the test. Exceptions (ask the operator first): throwaway prototypes, generated code, config.

When something breaks (root cause first)

NO FIXES WITHOUT FINDING THE ROOT CAUSE.

  1. Read the error message fully — it usually says what's wrong.
  2. Reproduce it reliably.
  3. Isolate the smallest failing case.
  4. Fix the cause, not the symptom. A patch that hides the symptom is a failure.

Test design

  • Test behaviour, not implementation detail.
  • Timing/wait deadlines must be generous (a max, returned-on-success). Tight deadlines flake in CI.
  • For provider/integration code, env-gate live tests so they're opt-in.

Platform

  • Branch builder/<TICKET> off latest main. Rebase, don't merge main in.
  • VCS depends on CW_VCS (default: cairn since 2026-07-09; CW_VCS=git opts out). In cairn mode the harness has already provisioned an isolated cairn working copy and dropped you inside your builder/<TICKET> line's folder — do not git-clone/branch; publish with cairn commit <branch> -m "…" && cairn push origin <branch> (exit-checked: exit 2 = conflicts, cairn resolve then re-commit before pushing). Load the cairn skill for the model. Open the PR with gh either way.
  • go build ./... and go test ./... must be green before the PR.
  • Frontend: browser-verify it (Playwright) before shipping. Don't ship UI you haven't seen rendered.
  • Before you finish, load the security skill and load the house-style skill, and apply them.

Done means

Branch pushed, single-ticket PR open, CI green (including security scans), PR description says what changed and how you verified it. Then load the review skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free