codewithmukesh/dotnet-claude-kit

checkpoint

Mid-session save point: create a descriptive git commit and a brief handoff note, then keep working.

Ver código-fonte
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

/checkpoint

What

A quick mid-session save that banks the known-good state in two moves:

  1. Descriptive git commit — stage relevant changes and commit with a

message that summarizes the work.

  1. Brief handoff note — write .claude/handoff.md so a resumed session

(or you, after a botched refactor) knows exactly where things stand.

Checkpoint is the mid-session save; /wrap-up is the end-of-session ritual. Checkpoint commits and jots a note, then keeps working. Wrap-up does the full handoff plus learning extraction into MEMORY.md.

When

  • Before a risky refactor or destructive change — checkpoint the known-good state
  • When switching to a different task or feature mid-session
  • After completing a logical unit of work — bank it
  • User says "checkpoint", "save progress", "save state", "pause here"
  • If the session is actually ending, use /wrap-up for the full ritual

How

  1. Assess stategit status and git diff to see staged and unstaged

changes.

  1. Stage changes — Stage specific files; never git add -A. Exclude

generated files, build artifacts, and secrets (.env, credentials).

  1. Commit — Descriptive message following the repo's commit style

(conventional prefixes: feat:, fix:, refactor:). New commit, never amend. If there is nothing to commit, skip to the handoff.

  1. Write handoff note.claude/handoff.md, same format as /wrap-up

but abbreviated: Completed, Pending (with specific next steps), Learned (only if something non-obvious surfaced), and Context (branch + commit hash). One file, always overwritten.

  1. Confirm — Report the commit hash and the handoff summary, then resume

work.

Safety Rules

  • Never push, force-push, or touch remote branches
  • Never commit secrets
  • Never amend — a checkpoint is a new commit you can return to
  • No changes to commit? Update the handoff only

Example

User: /checkpoint — about to try the EF Core split-query refactor

Claude: 3 files modified, 1 new.

  Commit a1b2c3d: "feat: add CreateOrder validation with FluentValidation"
  - src/Orders/Features/CreateOrder.cs
  - src/Orders/Features/CreateOrderValidator.cs (new)
  - tests/Orders.Tests/Features/CreateOrderTests.cs

  Handoff updated (.claude/handoff.md):
  ## Completed
  - [x] CreateOrder validation + 3 test scenarios
  ## Pending
  - [ ] Split-query refactor in GetOrderDetails (about to attempt)
  ## Context
  - Branch: feature/order-validation | Checkpoint: a1b2c3d

  Checkpoint saved — safe to proceed with the risky refactor.

Related

  • /wrap-up — End-of-session ritual: full handoff format definition plus

learning extraction into MEMORY.md

  • /build-fix — Get the build green before checkpointing
do mesmo repositório

Mais Skills

Todos os Skills
codewithmukesh
Comunidade

api-versioning

API versioning strategies for ASP.NET Core. Covers Asp.Versioning library, URL segment, header, and query string strategies, version deprecation, and OpenAPI integration. Load this skill when adding versioning to an API, evolving an API with breaking changes, or when the user mentions "API version", "versioning", "v1/v2", "Asp.Versioning", "deprecation", "breaking change", or "backward compatibility".

instalações
2
GitHub Stars
692
Atualizado
7 de ago.
codewithmukesh
Comunidade

arch-check

Architecture conformance check: verifies an existing codebase against its declared architecture (VSA, Clean Architecture, DDD, Modular Monolith) — dependency direction, layer violations, module boundary leaks, and cycles — using token-cheap Roslyn MCP analysis. Invoke when: "check architecture", "architecture violations", "layer violations", "dependency direction", "module boundaries", "arch check", "is my architecture clean", "enforce architecture", "conformance check". For CHOOSING an architecture, use architecture-advisor instead.

instalações
2
GitHub Stars
692
Atualizado
7 de ago.
codewithmukesh
Comunidade

architecture-advisor

Architecture selection advisor for .NET applications. Asks structured questions about domain complexity, team size, system lifetime, compliance, and integration needs, then recommends the best-fit architecture: Vertical Slice, Clean Architecture, DDD + Clean Architecture, or Modular Monolith. Load this skill when the user asks "which architecture", "choose architecture", "set up project", "new project", "architecture decision", "restructure", or "how should I organize". Always load BEFORE any architecture-specific skill.

instalações
2
GitHub Stars
692
Atualizado
7 de ago.
codewithmukesh
Comunidade

aspire

.NET Aspire for cloud-native orchestration. Covers AppHost configuration, service defaults, resource configuration, service discovery, and the Aspire dashboard. Load this skill when setting up local development orchestration, service discovery, or Aspire-managed infrastructure, or when the user mentions "Aspire", "AppHost", "service defaults", "service discovery", "orchestration", "Aspire dashboard", "AddProject", "WithReference", or "cloud-native .NET".

instalações
2
GitHub Stars
692
Atualizado
7 de ago.