codemap-trust

Included with Lifetime

$97 forever

Use to assess confidence/risk per module. "Which parts of this codebase can I trust", "where's the risk concentrated". Outputs a trust map with reasoning.

General

What this skill does


# codemap-trust

Per-module trust assessment. Where can you confidently ship? Where do you tread carefully?

## Trust signals

- **Test coverage** — high cov = high signal (but coverage ≠ correctness)
- **Test quality** — assertions per test, edge case coverage, behaviour vs implementation
- **Churn** — high churn + low cov = unstable
- **Bus factor** — single committer = fragile
- **Documentation** — public API documented = trustworthy
- **Recent incidents** — `mem_search { kind: incident }` per module
- **Dependency stability** — pinned vs ^x.y.z; deps with security advisories
- **Type strictness** — `any` count per module

## Method

1. **Extract signals** per module via `Bash` (coverage report, git log, type-check output).
2. **Score** each module 0-5 per signal.
3. **Aggregate** to a trust score 0-5.
4. **Reason** for the score — name the strongest negative + strongest positive.
5. **Risk register** — modules at trust < 3 are flagged with mitigation.

## Output shape

```
Codebase:   <repo>

Trust scores:

  src/memory/         ⭐⭐⭐⭐⭐  (5/5)  high cov, recent activity, no incidents
  src/core/           ⭐⭐⭐⭐⭐  (5/5)  100% cov, recent
  src/services/       ⭐⭐⭐⭐☆  (4/5)  ported recently, some deps haven't run in CI
  src/utils/          ⭐⭐⭐⭐⭐  (5/5)  
  src/llm/            ⭐⭐☆☆☆  (2/5)  empty stubs only — placeholder

Risk register:
  src/llm/            unimplemented; flag for Phase E completion
                      Mitigation: scope out + complete stubs OR document as TODO

Trends:
  - Strong test culture across kept modules
  - One module (llm) needs completion before public release
```

## Rules

- **Score per signal.** Aggregate with reasoning, not handwave.
- **Risk register has mitigations.** Flagging without action is noise.
- **Trends matter.** Snapshot is one moment; trend reveals direction.
- **Compare to previous trust assessment** if one exists. Improvement / decline is interesting.

## Anti-patterns

- Aggregate-only score without per-signal breakdown
- Treating coverage as the only signal
- Ignoring memory of incidents per module
- Risk register without mitigations

## When NOT to use

- Tiny project — manual judgement faster
- All modules already trusted — overkill
- Pre-launch — by definition many modules are immature; trust grows

## Subagent dispatch

- `Bash` for signal extraction
- `Explore` for type-strictness sampling
- Memory MCP for incident lookups

## Value over native CC

CC will discuss code quality. CC won't naturally produce structured per-module trust scores with multi-signal reasoning. The structure IS the value — feeds prioritisation.

Files: 1

Size: 2.8 KB

Complexity: 6/100

Category: General

Source: https://github.com/ialameh/sift-coder/tree/main/skills/docs/codemap-trust

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts