Skip to content
cccskills
FreePublished on GitHub

nw-investigation-techniques

Evidence collection methods, problem categorization, analysis techniques, and solution design patterns

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Investigation Techniques

Problem Categorization

Technical Problems

CategorySub-CategoryCommon Symptoms
System FailuresApp crashes, memory leaks, deadlocks, data corruptionService unavailability, resource exhaustion, integrity errors
System FailuresHardware, network, database, securityConnectivity loss, capacity limits, access failures
PerformanceResponse time: slow queries, latency, algorithmic inefficiencyHigh p95/p99, user-reported slowness
PerformanceThroughput: thread pool exhaustion, connection limits, queue backlogReduced capacity, growing queues
IntegrationInternal: component comms, data format, version conflictsInterface errors, serialization failures
IntegrationExternal: third-party availability, API changes, auth failuresTimeouts, contract violations

Operational Problems

CategoryCommon Symptoms
Deployment: script failures, config drift, migration errorsFailed releases, environment inconsistencies
Monitoring: alerting gaps, backup failures, incident responseMissed incidents, slow recovery
Human factors: communication gaps, knowledge silos, skill gapsRepeated mistakes, slow onboarding

Evidence Collection

Technical Evidence Sources

Logs: application (timestamp correlation) | system/infrastructure | database | network traces

Metrics: performance/resource utilization | error rates/response time trends | user behavior/transaction patterns | infrastructure health/capacity

Configuration: system/deployment settings | code changes/VCS history (git log, blame) | env vars/dependencies | security/access controls

Evidence Validation

  1. Cross-reference: verify from multiple independent sources
  2. Timestamp validation: confirm event sequence accuracy
  3. Completeness check: identify data gaps/corruption
  4. Correlation vs causation: distinguish co-occurrence from causation

Analysis Techniques

Quantitative

  • Trend: time series of metrics, error pattern frequency
  • Distribution: response time percentiles, error rate across components
  • Pattern recognition: log anomalies, behavior patterns, error clustering

Qualitative

  • Timeline reconstruction: detailed incident timeline, correlate changes with symptoms
  • Process analysis: workflow disruptions, communication flow, decision chains
  • Environmental: recent changes, system load, external factors, related incidents

Solution Design Patterns

Immediate Mitigations (restore service)

Quick fixes | workarounds to minimize impact | emergency procedures | monitoring enhancements

Permanent Fixes (prevent recurrence)

Architecture modifications | code quality/defensive programming | config management/environment consistency | testing/validation improvements

Early Detection (catch faster)

Leading indicators | anomaly detection/predictive alerting | automated quality gates | threshold tuning from learnings

Solution Prioritization Matrix

PriorityCriteriaAction
P0Active incident, users impactedImmediate mitigation, hours
P1Root cause fix for recurring issuePermanent fix, current sprint
P2Prevention for potential issuesNext sprint
P3Systemic improvementBacklog with evidence

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

The English summary is being prepared. Showing the original description.

nWave-ai/nWave622Updated Sep 16, 2026

See all skills by nWave-ai

Report a problem with this skill