OpenSmartRoute

trellis-finish-work - Prompt - OpenSmartRoute

Promptv1.0.0

trellis-finish-work

Name: trellis-finish-work
Author: XIEMY0987

Before submitting or committing, use this checklist to ensure work completeness.

by XIEMY0987(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from XIEMY0987/hospital-medical-system (.cursor/commands/trellis-finish-work.md). Copyright stays with the author.

Finish Work - Pre-Commit Checklist

Before submitting or committing, use this checklist to ensure work completeness.

Timing: After code is written and tested, before commit

Checklist

1. Code Quality

# Must pass
pnpm lint
pnpm type-check
pnpm test

pnpm lint passes with 0 errors?
pnpm type-check passes with no type errors?
Tests pass?
No console.log statements (use logger)?
No non-null assertions (the x! operator)?
No any types?

2. Documentation Sync

Spec Docs:

Does .trellis/spec/backend/ need updates?
- New patterns, new modules, new conventions
Does .trellis/spec/frontend/ need updates?
- New components, new hooks, new patterns
Does .trellis/spec/guides/ need updates?
- New cross-layer flows, lessons from bugs

Key Question:

"If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"

If YES -> Update the relevant spec doc.

3. API Changes

If you modified API endpoints:

Input schema updated?
Output schema updated?
API documentation updated?
Client code updated to match?

4. Database Changes

If you modified database schema:

Migration file created?
Schema file updated?
Related queries updated?
Seed data updated (if applicable)?

5. Cross-Layer Verification

If the change spans multiple layers:

Data flows correctly through all layers?
Error handling works at each boundary?
Types are consistent across layers?
Loading states handled?

6. Manual Testing

Feature works in browser/app?
Edge cases tested?
Error states tested?
Works after page refresh?

Quick Check Flow

# 1. Code checks
pnpm lint && pnpm type-check

# 2. View changes
git status
git diff --name-only

# 3. Based on changed files, check relevant items above

Common Oversights

Oversight	Consequence	Check
Spec docs not updated	Others don't know the change	Check .trellis/spec/
Migration not created	Schema out of sync	Check db/migrations/
Types not synced	Runtime errors	Check shared types
Tests not updated	False confidence	Run full test suite
Console.log left in	Noisy production logs	Search for console.log

Relationship to Other Commands

Development Flow:
  Write code -> Test -> /trellis-finish-work -> git commit -> /trellis-record-session
                          |                              |
                   Ensure completeness              Record progress
                   
Debug Flow:
  Hit bug -> Fix -> /trellis-break-loop -> Knowledge capture
                       |
                  Deep analysis

/trellis-finish-work - Check work completeness (this command)
/trellis-record-session - Record session and commits
/trellis-break-loop - Deep analysis after debugging

Core Principle

Delivery includes not just code, but also documentation, verification, and knowledge capture.

Complete work = Code + Docs + Tests + Verification

Installed into a catalogue, chosen by a router

Install trellis-finish-work and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# Finish Work - Pre-Commit Checklist

Before submitting or committing, use this checklist to ensure work completeness.

**Timing**: After code is written and tested, before commit

---

## Checklist

### 1. Code Quality

```bash
# Must pass
pnpm lint
pnpm type-check
pnpm test
```

- [ ] `pnpm lint` passes with 0 errors?
- [ ] `pnpm type-check` passes with no type errors?
- [ ] Tests pass?
- [ ] No `console.log` statements (use logger)?
- [ ] No non-null assertions (the `x!` operator)?
- [ ] No `any` types?

### 2. Documentation Sync

**Spec Docs**:
- [ ] Does `.trellis/spec/backend/` need updates?
  - New patterns, new modules, new conventions
- [ ] Does `.trellis/spec/frontend/` need updates?
  - New components, new hooks, new patterns
- [ ] Does `.trellis/spec/guides/` need updates?
  - New cross-layer flows, lessons from bugs

**Key Question**: 
> "If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"

If YES -> Update the relevant spec doc.

### 3. API Changes

If you modified API endpoints:

- [ ] Input schema updated?
- [ ] Output schema updated?
- [ ] API documentation updated?
- [ ] Client code updated to match?

### 4. Database Changes

If you modified database schema:

- [ ] Migration file created?
- [ ] Schema file updated?
- [ ] Related queries updated?
- [ ] Seed data updated (if applicable)?

### 5. Cross-Layer Verification

If the change spans multiple layers:

- [ ] Data flows correctly through all layers?
- [ ] Error handling works at each boundary?
- [ ] Types are consistent across layers?
- [ ] Loading states handled?

### 6. Manual Testing

- [ ] Feature works in browser/app?
- [ ] Edge cases tested?
- [ ] Error states tested?
- [ ] Works after page refresh?

---

## Quick Check Flow

```bash
# 1. Code checks
pnpm lint && pnpm type-check

# 2. View changes
git status
git diff --name-only

# 3. Based on changed files, check relevant items above
```

---

## Common Oversights

| Oversight | Consequence | Check |
|-----------|-------------|-------|
| Spec docs not updated | Others don't know the change | Check .trellis/spec/ |
| Migration not created | Schema out of sync | Check db/migrations/ |
| Types not synced | Runtime errors | Check shared types |
| Tests not updated | False confidence | Run full test suite |
| Console.log left in | Noisy production logs | Search for console.log |

---

## Relationship to Other Commands

```
Development Flow:
  Write code -> Test -> /trellis-finish-work -> git commit -> /trellis-record-session
                          |                              |
                   Ensure completeness              Record progress
                   
Debug Flow:
  Hit bug -> Fix -> /trellis-break-loop -> Knowledge capture
                       |
                  Deep analysis
```

- `/trellis-finish-work` - Check work completeness (this command)
- `/trellis-record-session` - Record session and commits
- `/trellis-break-loop` - Deep analysis after debugging

---

## Core Principle

> **Delivery includes not just code, but also documentation, verification, and knowledge capture.**

Complete work = Code + Docs + Tests + Verification

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

xiemy0987-hospital-medical-system-trellis-finish-work-cu-0c0889.prompt.jsonjson

{
  "prompt": "# Finish Work - Pre-Commit Checklist\n\nBefore submitting or committing, use this checklist to ensure work completeness.\n\n**Timing**: After code is written and tested, before commit\n\n---\n\n## Checklist\n\n### 1. Code Quality\n\n```bash\n# Must pass\npnpm lint\npnpm type-check\npnpm test\n```\n\n- [ ] `pnpm lint` passes with 0 errors?\n- [ ] `pnpm type-check` passes with no type errors?\n- [ ] Tests pass?\n- [ ] No `console.log` statements (use logger)?\n- [ ] No non-null assertions (the `x!` operator)?\n- [ ] No `any` types?\n\n### 2. Documentation Sync\n\n**Spec Docs**:\n- [ ] Does `.trellis/spec/backend/` need updates?\n  - New patterns, new modules, new conventions\n- [ ] Does `.trellis/spec/frontend/` need updates?\n  - New components, new hooks, new patterns\n- [ ] Does `.trellis/spec/guides/` need updates?\n  - New cross-layer flows, lessons from bugs\n\n**Key Question**: \n> \"If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?\"\n\nIf YES -> Update the relevant spec doc.\n\n### 3. API Changes\n\nIf you modified API endpoints:\n\n- [ ] Input schema updated?\n- [ ] Output schema updated?\n- [ ] API documentation updated?\n- [ ] Client code updated to match?\n\n### 4. Database Changes\n\nIf you modified database schema:\n\n- [ ] Migration file created?\n- [ ] Schema file updated?\n- [ ] Related queries updated?\n- [ ] Seed data updated (if applicable)?\n\n### 5. Cross-Layer Verification\n\nIf the change spans multiple layers:\n\n- [ ] Data flows correctly through all layers?\n- [ ] Error handling works at each boundary?\n- [ ] Types are consistent across layers?\n- [ ] Loading states handled?\n\n### 6. Manual Testing\n\n- [ ] Feature works in browser/app?\n- [ ] Edge cases tested?\n- [ ] Error states tested?\n- [ ] Works after page refresh?\n\n---\n\n## Quick Check Flow\n\n```bash\n# 1. Code checks\npnpm lint && pnpm type-check\n\n# 2. View changes\ngit status\ngit diff --name-only\n\n# 3. Based on changed files, check relevant items above\n```\n\n---\n\n## Common Oversights\n\n| Oversight | Consequence | Check |\n|-----------|-------------|-------|\n| Spec docs not updated | Others don't know the change | Check .trellis/spec/ |\n| Migration not created | Schema out of sync | Check db/migrations/ |\n| Types not synced | Runtime errors | Check shared types |\n| Tests not updated | False confidence | Run full test suite |\n| Console.log left in | Noisy production logs | Search for console.log |\n\n---\n\n## Relationship to Other Commands\n\n```\nDevelopment Flow:\n  Write code -> Test -> /trellis-finish-work -> git commit -> /trellis-record-session\n                          |                              |\n                   Ensure completeness              Record progress\n                   \nDebug Flow:\n  Hit bug -> Fix -> /trellis-break-loop -> Knowledge capture\n                       |\n                  Deep analysis\n```\n\n- `/trellis-finish-work` - Check work completeness (this command)\n- `/trellis-record-session` - Record session and commits\n- `/trellis-break-loop` - Deep analysis after debugging\n\n---\n\n## Core Principle\n\n> **Delivery includes not just code, but also documentation, verification, and knowledge capture.**\n\nComplete work = Code + Docs + Tests + Verification",
  "variables": [],
  "notes": "Before submitting or committing, use this checklist to ensure work completeness.",
  "metadata": {
    "source": {
      "provider": "github-cursor-commands",
      "repository": "https://github.com/XIEMY0987/hospital-medical-system",
      "path": ".cursor/commands/trellis-finish-work.md",
      "ref": "2a4aeb7a83dcaefa0d4b8a021a22f8fae65ba766",
      "url": "https://github.com/XIEMY0987/hospital-medical-system/blob/2a4aeb7a83dcaefa0d4b8a021a22f8fae65ba766/.cursor/commands/trellis-finish-work.md",
      "key": "XIEMY0987/hospital-medical-system/.cursor/commands/trellis-finish-work.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/xiemy0987-hospital-medical-system-trellis-finish-work-cu-0c0889/manifest?version=1.0.0