skills:retrospective

Engineering Community

Skill notes

Table of Contents

When to Use Phase 1: Analysis Phase 2: Skill Inventory Review Phase 3: Create Plan Phase 4: Execute with Approval

When to Use

Run at the end of significant sessions: After debugging a complex issue After implementing a new feature After onboarding to a new area of the codebase When you notice repeated patterns

Phase 1: Session Analysis

Review the current session for patterns. Do NOT make changes yet.

1.1 Repeated Commands

What commands did you run more than 3 times?

1.2 Long Debugging Cycles

What took longest to figure out? Did I try multiple approaches before finding the right one? Was there a "trick" that finally worked? Would a checklist have helped?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@kagenti · no license declared
Token usage
Moderate
Setup complexity
Guided setup
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
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

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

01
Phase 1: Session Analysis

Review the current session for patterns. Do NOT make changes yet.

02
Phase 1b: Commit History Analysis

Analyze recent commit history to identify blind paths and wasted iterations.

03
Phase 2: Skill Inventory Review

Review existing skills for refactoring opportunities. Do NOT make changes yet.

04
Phase 3: Create Plan

Write a plan document for approval. Include all proposed changes.

05
Phase 4: Execute with Approval

Only after user approves the plan, execute changes.

Discussion

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