contribute

To turn a workspace lesson into a reusable contribution, you generalize the specific finding into project-agnostic guidance. The process applies a mandatory sanitizer to detect and block private context, then stages a reviewable contribution file for later pull-in.

A sanitized contribution file for project session memory is a reviewable record containing the type, target, problem, recommendation, and rationale of a generalized improvement. It applies sanitizer validation to ensure no private implementation details are exposed before staging.

You generalize a project-specific fix into portable skill updates by rewriting the finding to apply across projects. This requires scope resolution from active session markers to ensure the improvement applies broadly before creating the contribution file.

Yes, the sanitizer validation stops the staging process if it detects secrets, private context, or tone issues. This mandatory check ensures only safe, project-agnostic contributions are staged for later pull-in into the shared skill set.

Before staging a configuration change contribution, you need scope resolution from active session markers. This determines the target files and ensures the generalized problem, recommendation, and rationale are properly structured for review.

You should not use an automated generalization process for workspace conventions when the lesson cannot be rewritten without referencing private context or specific implementation details. If the sanitizer validation fails and the finding remains project-specific, it cannot be staged safely.