devskill 2.0.7 → 2.0.8

package/skills/sponsor-finder/SKILL.md

@@ -0,0 +1,258 @@
+---
+name: sponsor-finder
+description: Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express").
+---
+
+# Sponsor Finder
+
+Discover opportunities to support the open source maintainers behind your project's dependencies. Accepts a GitHub `owner/repo` (e.g. `/sponsor expressjs/express`), uses the deps.dev API for dependency resolution and project health data, and produces a friendly sponsorship report covering both direct and transitive dependencies.
+
+## Your Workflow
+
+When the user types `/sponsor {owner/repo}` or provides a repository in `owner/repo` format:
+
+1. **Parse the input** — Extract `owner` and `repo`.
+2. **Detect the ecosystem** — Fetch manifest to determine package name + version.
+3. **Get full dependency tree** — deps.dev `GetDependencies` (one call).
+4. **Resolve repos** — deps.dev `GetVersion` for each dep → `relatedProjects` gives GitHub repo.
+5. **Get project health** — deps.dev `GetProject` for unique repos → OSSF Scorecard.
+6. **Find funding links** — npm `funding` field, FUNDING.yml, web search fallback.
+7. **Verify every link** — fetch each URL to confirm it's live.
+8. **Group and report** — by funding destination, sorted by impact.
+
+---
+
+## Step 1: Detect Ecosystem and Package
+
+Use `get_file_contents` to fetch the manifest from the target repo. Determine the ecosystem and extract the package name + latest version:
+
+| File | Ecosystem | Package name from | Version from |
+|------|-----------|-------------------|--------------|
+| `package.json` | NPM | `name` field | `version` field |
+| `requirements.txt` | PYPI | list of package names | use latest (omit version in deps.dev call) |
+| `pyproject.toml` | PYPI | `[project.dependencies]` | use latest |
+| `Cargo.toml` | CARGO | `[package] name` | `[package] version` |
+| `go.mod` | GO | `module` path | extract from go.mod |
+| `Gemfile` | RUBYGEMS | gem names | use latest |
+| `pom.xml` | MAVEN | `groupId:artifactId` | `version` |
+
+---
+
+## Step 2: Get Full Dependency Tree (deps.dev)
+
+**This is the key step.** Use `web_fetch` to call the deps.dev API:
+
+```
+https://api.deps.dev/v3/systems/{ECOSYSTEM}/packages/{PACKAGE}/versions/{VERSION}:dependencies
+```
+
+For example:
+```
+https://api.deps.dev/v3/systems/npm/packages/express/versions/5.2.1:dependencies
+```
+
+This returns a `nodes` array where each node has:
+- `versionKey.name` — package name
+- `versionKey.version` — resolved version
+- `relation` — `"SELF"`, `"DIRECT"`, or `"INDIRECT"`
+
+**This single call gives you the entire dependency tree** — both direct and transitive — with exact resolved versions. No need to parse lockfiles.
+
+### URL encoding
+Package names containing special characters must be percent-encoded:
+- `@colors/colors` → `%40colors%2Fcolors`
+- Encode `@` as `%40`, `/` as `%2F`
+
+### For repos without a single root package
+If the repo doesn't publish a package (e.g., it's an app not a library), fall back to reading `package.json` dependencies directly and calling deps.dev `GetVersion` for each.
+
+---
+
+## Step 3: Resolve Each Dependency to a GitHub Repo (deps.dev)
+
+For each dependency from the tree, call deps.dev `GetVersion`:
+
+```
+https://api.deps.dev/v3/systems/{ECOSYSTEM}/packages/{NAME}/versions/{VERSION}
+```
+
+From the response, extract:
+- **`relatedProjects`** → look for `relationType: "SOURCE_REPO"` → `projectKey.id` gives `github.com/{owner}/{repo}`
+- **`links`** → look for `label: "SOURCE_REPO"` → `url` field
+
+This works across **all ecosystems** — npm, PyPI, Cargo, Go, RubyGems, Maven, NuGet — with the same field structure.
+
+### Efficiency rules
+- Process in batches of **10 at a time**.
+- Deduplicate — multiple packages may map to the same repo.
+- Skip deps where no GitHub project is found (count as "unresolvable").
+
+---
+
+## Step 4: Get Project Health Data (deps.dev)
+
+For each unique GitHub repo, call deps.dev `GetProject`:
+
+```
+https://api.deps.dev/v3/projects/github.com%2F{owner}%2F{repo}
+```
+
+From the response, extract:
+- **`scorecard.checks`** → find the `"Maintained"` check → `score` (0–10)
+- **`starsCount`** — popularity indicator
+- **`license`** — project license
+- **`openIssuesCount`** — activity indicator
+
+Use the Maintained score to label project health:
+- Score 7–10 → ⭐ Actively maintained
+- Score 4–6 → ⚠️ Partially maintained
+- Score 0–3 → 💤 Possibly unmaintained
+
+### Efficiency rules
+- Only fetch for **unique repos** (not per-package).
+- Process in batches of **10 at a time**.
+- This step is optional — skip if rate-limited and note in output.
+
+---
+
+## Step 5: Find Funding Links
+
+For each unique GitHub repo, check for funding information using three sources in order:
+
+### 5a: npm `funding` field (npm ecosystem only)
+Use `web_fetch` on `https://registry.npmjs.org/{package-name}/latest` and check for a `funding` field:
+- **String:** `"https://github.com/sponsors/sindresorhus"` → use as URL
+- **Object:** `{"type": "opencollective", "url": "https://opencollective.com/express"}` → use `url`
+- **Array:** collect all URLs
+
+### 5b: `.github/FUNDING.yml` (repo-level, then org-level fallback)
+
+**Step 5b-i — Per-repo check:**
+Use `get_file_contents` to fetch `{owner}/{repo}` path `.github/FUNDING.yml`.
+
+**Step 5b-ii — Org/user-level fallback:**
+If 5b-i returned 404 (no FUNDING.yml in the repo itself), check the owner's default community health repo:
+Use `get_file_contents` to fetch `{owner}/.github` path `FUNDING.yml`.
+
+GitHub supports a [default community health files](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) convention: a `.github` repository at the user/org level provides defaults for all repos that lack their own. For example, `isaacs/.github/FUNDING.yml` applies to all `isaacs/*` repos.
+
+Only look up each unique `{owner}/.github` repo **once** — reuse the result for all repos under that owner. Process in batches of **10 owners at a time**.
+
+Parse the YAML (same for both 5b-i and 5b-ii):
+- `github: [username]` → `https://github.com/sponsors/{username}`
+- `open_collective: slug` → `https://opencollective.com/{slug}`
+- `ko_fi: username` → `https://ko-fi.com/{username}`
+- `patreon: username` → `https://patreon.com/{username}`
+- `tidelift: platform/package` → `https://tidelift.com/subscription/pkg/{platform-package}`
+- `custom: [urls]` → use as-is
+
+### 5c: Web search fallback
+For the **top 10 unfunded dependencies** (by number of transitive dependents), use `web_search`:
+```
+"{package name}" github sponsors OR open collective OR funding
+```
+Skip packages known to be corporate-maintained (React/Meta, TypeScript/Microsoft, @types/DefinitelyTyped).
+
+### Efficiency rules
+- **Check 5a and 5b for all deps.** Only use 5c for top unfunded ones.
+- Skip npm registry calls for non-npm ecosystems.
+- Deduplicate repos — check each repo only once.
+- **One `{owner}/.github` check per unique owner** — reuse the result for all their repos.
+- Process org-level lookups in batches of **10 owners at a time**.
+
+---
+
+## Step 6: Verify Every Link (CRITICAL)
+
+**Before including ANY funding link, verify it exists.**
+
+Use `web_fetch` on each funding URL:
+- **Valid page** → ✅ Include
+- **404 / "not found" / "not enrolled"** → ❌ Exclude
+- **Redirect to valid page** → ✅ Include final URL
+
+Verify in batches of **5 at a time**. Never present unverified links.
+
+---
+
+## Step 7: Output the Report
+
+### Output discipline
+
+**Minimize intermediate output during data gathering.** Do NOT announce each batch ("Batch 3 of 7…", "Now checking funding…"). Instead:
+- Show **one brief status line** when starting each major phase (e.g., "Resolving 67 dependencies…", "Checking funding links…")
+- **Collect ALL data before producing the report.** Never drip-feed partial tables.
+- Output the final report as a **single cohesive block** at the end.
+
+### Report template
+
+```
+## 💜 Sponsor Finder Report
+
+**Repository:** {owner}/{repo} · {ecosystem} · {package}@{version}
+**Scanned:** {date} · {total} deps ({direct} direct + {transitive} transitive)
+
+---
+
+### 🎯 Ways to Give Back
+
+Sponsoring just {N} people/orgs supports {sponsorable} of your {total} dependencies — a great way to invest in the open source your project depends on.
+
+1. **💜 @{user}** — {N} direct + {M} transitive deps · ⭐ Maintained
+   {dep1}, {dep2}, {dep3}, ...
+   https://github.com/sponsors/{user}
+
+2. **🟠 Open Collective: {name}** — {N} direct + {M} transitive deps · ⭐ Maintained
+   {dep1}, {dep2}, {dep3}, ...
+   https://opencollective.com/{name}
+
+3. **💜 @{user2}** — {N} direct dep · 💤 Low activity
+   {dep1}
+   https://github.com/sponsors/{user2}
+
+---
+
+### 📊 Coverage
+
+- **{sponsorable}/{total}** dependencies have funding options ({percentage}%)
+- **{destinations}** unique funding destinations
+- **{unfunded_direct}** direct deps don't have funding set up yet ({top_names}, ...)
+- All links verified ✅
+```
+
+### Report format rules
+
+- **Lead with "🎯 Ways to Give Back"** — this is the primary output. Numbered list, sorted by total deps covered (descending).
+- **Bare URLs on their own line** — not wrapped in markdown link syntax. This ensures they're clickable in any terminal emulator.
+- **Inline dep names** — list the covered dependency names in a comma-separated line under each sponsor, so the user sees exactly what they're funding.
+- **Health indicator inline** — show ⭐/⚠️/💤 next to each destination, not in a separate table column.
+- **One "📊 Coverage" section** — compact stats. No separate "Verified Funding Links" table, no "No Funding Found" table.
+- **Unfunded deps as a brief note** — just the count + top names. Frame as "don't have funding set up yet" rather than highlighting a gap. Never shame projects for not having funding — many maintainers prefer other forms of contribution.
+- 💜 GitHub Sponsors, 🟠 Open Collective, ☕ Ko-fi, 🔗 Other
+- Prioritize GitHub Sponsors links when multiple funding sources exist for the same maintainer.
+
+---
+
+## Error Handling
+
+- If deps.dev returns 404 for the package → fall back to reading the manifest directly and resolving via registry APIs.
+- If deps.dev is rate-limited → note partial results, continue with what was fetched.
+- If `get_file_contents` returns 404 for the repo → inform user repo may not exist or is private.
+- If link verification fails → exclude the link silently.
+- Always produce a report even if partial — never fail silently.
+
+---
+
+## Critical Rules
+
+1. **NEVER present unverified links.** Fetch every URL before showing it. 5 verified links > 20 guessed links.
+2. **NEVER guess from training knowledge.** Always check — funding pages change over time.
+3. **Always be encouraging, never shaming.** Frame results positively — celebrate what IS funded, and treat unfunded deps as an opportunity, not a failing. Not every project needs or wants financial sponsorship.
+4. **Lead with action.** The "🎯 Ways to Give Back" section is the primary output — bare clickable URLs, grouped by destination.
+5. **Use deps.dev as primary resolver.** Fall back to registry APIs only if deps.dev is unavailable.
+6. **Always use GitHub MCP tools** (`get_file_contents`), `web_fetch`, and `web_search` — never clone or shell out.
+7. **Be efficient.** Batch API calls, deduplicate repos, check each owner's `.github` repo only once.
+8. **Focus on GitHub Sponsors.** Most actionable platform — show others but prioritize GitHub.
+9. **Deduplicate by maintainer.** Group to show real impact of sponsoring one person.
+10. **Show the actionable minimum.** Tell users the fewest sponsorships to support the most deps.
+11. **Minimize intermediate output.** Don't announce each batch. Collect all data, then output one cohesive report.

package/skills/sponsor-finder/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/sponsor-finder`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/spring-boot-testing/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/spring-boot-testing/SKILL.md

@@ -0,0 +1,189 @@
+---
+name: spring-boot-testing
+description: Expert Spring Boot 4 testing specialist that selects the best Spring Boot testing techniques for your situation with Junit 6 and AssertJ.
+---
+
+# Spring Boot Testing
+
+This skill provides expert guide for testing Spring Boot 4 applications with modern patterns and best practices.
+
+## Core Principles
+
+1. **Test Pyramid**: Unit (fast) > Slice (focused) > Integration (complete)
+2. **Right Tool**: Use the narrowest slice that gives you confidence
+3. **AssertJ Style**: Fluent, readable assertions over verbose matchers
+4. **Modern APIs**: Prefer MockMvcTester and RestTestClient over legacy alternatives
+
+## Which Test Slice?
+
+| Scenario | Annotation | Reference |
+|----------|------------|-----------|
+| Controller + HTTP semantics | `@WebMvcTest` | [references/webmvctest.md](references/webmvctest.md) |
+| Repository + JPA queries | `@DataJpaTest` | [references/datajpatest.md](references/datajpatest.md) |
+| REST client + external APIs | `@RestClientTest` | [references/restclienttest.md](references/restclienttest.md) |
+| JSON (de)serialization | `@JsonTest` | [references/test-slices-overview.md](references/test-slices-overview.md) |
+| Full application | `@SpringBootTest` | [references/test-slices-overview.md](references/test-slices-overview.md) |
+
+## Test Slices Reference
+
+- [references/test-slices-overview.md](references/test-slices-overview.md) - Decision matrix and comparison
+- [references/webmvctest.md](references/webmvctest.md) - Web layer with MockMvc
+- [references/datajpatest.md](references/datajpatest.md) - Data layer with Testcontainers
+- [references/restclienttest.md](references/restclienttest.md) - REST client testing
+
+## Testing Tools Reference
+
+- [references/mockmvc-tester.md](references/mockmvc-tester.md) - AssertJ-style MockMvc (3.2+)
+- [references/mockmvc-classic.md](references/mockmvc-classic.md) - Traditional MockMvc (pre-3.2)
+- [references/resttestclient.md](references/resttestclient.md) - Spring Boot 4+ REST client
+- [references/mockitobean.md](references/mockitobean.md) - Mocking dependencies
+
+## Assertion Libraries
+
+- [references/assertj-basics.md](references/assertj-basics.md) - Scalars, strings, booleans, dates
+- [references/assertj-collections.md](references/assertj-collections.md) - Lists, Sets, Maps, arrays
+
+## Testcontainers
+
+- [references/testcontainers-jdbc.md](references/testcontainers-jdbc.md) - PostgreSQL, MySQL, etc.
+
+## Test Data Generation
+
+- [references/instancio.md](references/instancio.md) - Generate complex test objects (3+ properties)
+
+## Performance & Migration
+
+- [references/context-caching.md](references/context-caching.md) - Speed up test suites
+- [references/sb4-migration.md](references/sb4-migration.md) - Spring Boot 4.0 changes
+
+## Quick Decision Tree
+
+```
+Testing a controller endpoint?
+  Yes → @WebMvcTest with MockMvcTester
+
+Testing repository queries?
+  Yes → @DataJpaTest with Testcontainers (real DB)
+
+Testing business logic in service?
+  Yes → Plain JUnit + Mockito (no Spring context)
+
+Testing external API client?
+  Yes → @RestClientTest with MockRestServiceServer
+
+Testing JSON mapping?
+  Yes → @JsonTest
+
+Need full integration test?
+  Yes → @SpringBootTest with minimal context config
+```
+
+## Spring Boot 4 Highlights
+
+- **RestTestClient**: Modern alternative to TestRestTemplate
+- **@MockitoBean**: Replaces @MockBean (deprecated)
+- **MockMvcTester**: AssertJ-style assertions for web tests
+- **Modular starters**: Technology-specific test starters
+- **Context pausing**: Automatic pausing of cached contexts (Spring Framework 7)
+
+## Testing Best Practices
+
+### Code Complexity Assessment
+
+When a method or class is too complex to test effectively:
+
+1. **Analyze complexity** - If you need more than 5-7 test cases to cover a single method, it's likely too complex
+2. **Recommend refactoring** - Suggest breaking the code into smaller, focused functions
+3. **User decision** - If the user agrees to refactor, help identify extraction points
+4. **Proceed if needed** - If the user decides to continue with the complex code, implement tests despite the difficulty
+
+**Example of refactoring recommendation:**
+```java
+// Before: Complex method hard to test
+public Order processOrder(OrderRequest request) {
+  // Validation, discount calculation, payment, inventory, notification...
+  // 50+ lines of mixed concerns
+}
+
+// After: Refactored into testable units
+public Order processOrder(OrderRequest request) {
+  validateOrder(request);
+  var order = createOrder(request);
+  applyDiscount(order);
+  processPayment(order);
+  updateInventory(order);
+  sendNotification(order);
+  return order;
+}
+```
+
+### Avoid Code Redundancy
+
+Create helper methods for commonly used objects and mock setup to enhance readability and maintainability.
+
+### Test Organization with @DisplayName
+
+Use descriptive display names to clarify test intent:
+
+```java
+@Test
+@DisplayName("Should calculate discount for VIP customer")
+void shouldCalculateDiscountForVip() { }
+
+@Test
+@DisplayName("Should reject order when customer has insufficient credit")
+void shouldRejectOrderForInsufficientCredit() { }
+```
+
+### Test Coverage Order
+
+Always structure tests in this order:
+
+1. **Main scenario** - The happy path, most common use case
+2. **Other paths** - Alternative valid scenarios, edge cases
+3. **Exceptions/Errors** - Invalid inputs, error conditions, failure modes
+
+### Test Production Scenarios
+
+Write tests with real production scenarios in mind. This makes tests more relatable and helps understand code behavior in actual production cases.
+
+### Test Coverage Goals
+
+Aim for 80% code coverage as a practical balance between quality and effort. Higher coverage is beneficial but not the only goal.
+
+Use Jacoco maven plugin for coverage reporting and tracking.
+
+
+**Coverage Rules:**
+- 80+% coverage minimum
+- Focus on meaningful assertions, not just execution
+
+**What to Prioritize:**
+1. Business-critical paths (payment processing, order validation)
+2. Complex algorithms (pricing, discount calculations)
+3. Error handling (exceptions, edge cases)
+4. Integration points (external APIs, databases)
+
+## Dependencies (Spring Boot 4)
+
+```xml
+<dependency>
+  <groupId>org.springframework.boot</groupId>
+  <artifactId>spring-boot-starter-test</artifactId>
+  <scope>test</scope>
+</dependency>
+
+<!-- For WebMvc tests -->
+<dependency>
+  <groupId>org.springframework.boot</groupId>
+  <artifactId>spring-boot-starter-webmvc-test</artifactId>
+  <scope>test</scope>
+</dependency>
+
+<!-- For Testcontainers -->
+<dependency>
+  <groupId>org.springframework.boot</groupId>
+  <artifactId>spring-boot-testcontainers</artifactId>
+  <scope>test</scope>
+</dependency>
+```

package/skills/spring-boot-testing/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/spring-boot-testing`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/spring-boot-testing/references/assertj-basics.md

@@ -0,0 +1,207 @@
+# AssertJ Basics
+
+Fluent assertions for readable, maintainable tests.
+
+## Basic Assertions
+
+### Object Equality
+
+```java
+assertThat(order.getStatus()).isEqualTo("PENDING");
+assertThat(order.getId()).isNotEqualTo(0);
+assertThat(order).isEqualTo(expectedOrder);
+assertThat(order).isNotNull();
+assertThat(nullOrder).isNull();
+```
+
+### String Assertions
+
+```java
+assertThat(order.getDescription())
+  .isEqualTo("Test Order")
+  .startsWith("Test")
+  .endsWith("Order")
+  .contains("Test")
+  .hasSize(10)
+  .matches("[A-Za-z ]+");
+```
+
+### Number Assertions
+
+```java
+assertThat(order.getAmount())
+  .isEqualTo(99.99)
+  .isGreaterThan(50)
+  .isLessThan(100)
+  .isBetween(50, 100)
+  .isPositive()
+  .isNotZero();
+```
+
+### Boolean Assertions
+
+```java
+assertThat(order.isActive()).isTrue();
+assertThat(order.isDeleted()).isFalse();
+```
+
+## Date/Time Assertions
+
+```java
+assertThat(order.getCreatedAt())
+  .isEqualTo(LocalDateTime.of(2024, 1, 15, 10, 30))
+  .isBefore(LocalDateTime.now())
+  .isAfter(LocalDateTime.of(2024, 1, 1))
+  .isCloseTo(LocalDateTime.now(), within(5, ChronoUnit.SECONDS));
+```
+
+## Optional Assertions
+
+```java
+Optional<Order> maybeOrder = orderService.findById(1L);
+
+assertThat(maybeOrder)
+  .isPresent()
+  .hasValueSatisfying(order -> {
+    assertThat(order.getId()).isEqualTo(1L);
+  });
+
+assertThat(orderService.findById(999L)).isEmpty();
+```
+
+## Exception Assertions
+
+### JUnit 5 Exception Handling
+
+```java
+@Test
+void shouldThrowException() {
+  OrderService service = new OrderService();
+  
+  assertThatThrownBy(() -> service.findById(999L))
+    .isInstanceOf(OrderNotFoundException.class)
+    .hasMessage("Order 999 not found")
+    .hasMessageContaining("999");
+}
+```
+
+### AssertJ Exception Handling
+
+```java
+@Test
+void shouldThrowExceptionWithCause() {
+  assertThatExceptionOfType(OrderProcessingException.class)
+    .isThrownBy(() -> service.processOrder(invalidOrder))
+    .withCauseInstanceOf(ValidationException.class);
+}
+```
+
+## Custom Assertions
+
+Create domain-specific assertions for reusable test code:
+
+```java
+public class OrderAssert extends AbstractAssert<OrderAssert, Order> {
+  
+  public static OrderAssert assertThat(Order actual) {
+    return new OrderAssert(actual);
+  }
+  
+  private OrderAssert(Order actual) {
+    super(actual, OrderAssert.class);
+  }
+  
+  public OrderAssert isPending() {
+    isNotNull();
+    if (!"PENDING".equals(actual.getStatus())) {
+      failWithMessage("Expected order status to be PENDING but was %s", actual.getStatus());
+    }
+    return this;
+  }
+  
+  public OrderAssert hasTotal(BigDecimal expected) {
+    isNotNull();
+    if (!expected.equals(actual.getTotal())) {
+      failWithMessage("Expected total %s but was %s", expected, actual.getTotal());
+    }
+    return this;
+  }
+}
+```
+
+Usage:
+
+```java
+OrderAssert.assertThat(order)
+  .isPending()
+  .hasTotal(new BigDecimal("99.99"));
+```
+
+## Soft Assertions
+
+Collect multiple failures before failing:
+
+```java
+@Test
+void shouldValidateOrder() {
+  Order order = orderService.findById(1L);
+  
+  SoftAssertions.assertSoftly(softly -> {
+    softly.assertThat(order.getId()).isEqualTo(1L);
+    softly.assertThat(order.getStatus()).isEqualTo("PENDING");
+    softly.assertThat(order.getItems()).isNotEmpty();
+  });
+}
+```
+
+## Satisfies Pattern
+
+```java
+assertThat(order)
+  .satisfies(o -> {
+    assertThat(o.getId()).isPositive();
+    assertThat(o.getStatus()).isNotBlank();
+    assertThat(o.getCreatedAt()).isNotNull();
+  });
+```
+
+## Using with Spring
+
+```java
+import static org.assertj.core.api.Assertions.assertThat;
+
+@SpringBootTest
+class OrderServiceTest {
+  
+  @Autowired
+  private OrderService orderService;
+  
+  @Test
+  void shouldCreateOrder() {
+    Order order = orderService.create(new OrderRequest("Product", 2));
+    
+    assertThat(order)
+      .isNotNull()
+      .extracting(Order::getId, Order::getStatus)
+      .containsExactly(1L, "PENDING");
+  }
+}
+```
+
+## Static Import
+
+Always use static import for clean assertions:
+
+```java
+import static org.assertj.core.api.Assertions.assertThat;
+import static org.assertj.core.api.Assertions.assertThatThrownBy;
+import static org.assertj.core.api.Assertions.catchThrowable;
+```
+
+## Key Benefits
+
+1. **Readable**: Sentence-like structure
+2. **Type-safe**: IDE autocomplete works
+3. **Rich API**: Many built-in assertions
+4. **Extensible**: Custom assertions for your domain
+5. **Better Errors**: Clear failure messages