thoroughness

Other Community

Skill notes

Purpose

This skill ensures comprehensive, complete implementation of complex tasks without shortcuts. Use this when quality and completeness matter more than speed.

When to Use

Fixing critical bugs or compilation errors Implementing complex multi-step features Debugging test failures Refactoring large codebases Production deployments

Phase 1: Comprehensive Analysis (20% of time)

Identify All Issues List every error, warning, and failing test Group related issues together Prioritize by dependency order Create issue hierarchy (what blocks what)

Phase 2: Systematic Implementation (60% of time)

Fix Issues in Dependency Order Start with foundational issues Fix one thing completely before moving on Test after each fix Document what was changed and why

Phase 3: Comprehensive Verification (20% of time)

Run All Tests Unit tests Integration tests E2E tests Manual verification

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@pr-pm · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Comprehensive Analysis (20% of time)

Identify All Issues List every error, warning, and failing test Group related issues together Prioritize by dependency order Create issue hierarchy (what blocks what)

02
Phase 2: Systematic Implementation (60% of time)

Fix Issues in Dependency Order Start with foundational issues Fix one thing completely before moving on Test after each fix Document what was changed and why

03
Phase 3: Comprehensive Verification (20% of time)

Run All Tests Unit tests Integration tests E2E tests Manual verification

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.