edit-log

Review build logs for risky language and internal references.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/venturecrane/crane-console --skill edit-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-log
Source: https://github.com/venturecrane/crane-console/tree/main/.agents/skills/edit-log
Command: npx skills add https://github.com/venturecrane/crane-console --skill edit-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides automated editorial review of build logs to ensure safe, genericized language and compliant references, reducing risk of leakage of internal details and improving readability.

Core Features & Use Cases

  • Blocking checks enforce exact textual fixes for terminology and internal references.
  • Cross-reference validation uses the terminology doc and venture registry to surface advisory items for human review.
  • Audit-ready output compiles a clean, generic log suitable for production reporting.

Quick Start

Provide a build log path to run the editorial review.

Frequently Asked Questions about edit-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sanitize build logs to remove internal references before production release?

Sanitize build logs by identifying and replacing risky language and internal references to ensure genericization and compliance. This editorial review applies terminology guidance to produce a production-ready field report.

What is build log genericization and when do I need it?

Build log genericization is the editorial process of removing internal details and risky language to prevent leakage. You need it when preparing compliant, audit-ready field reports for production environments.

How do I enforce terminology compliance in automated build logs?

Enforce terminology compliance in build logs by applying blocking checks that execute exact textual fixes for internal references. The process cross-references terminology docs to ensure compliant output.

Can I automate editorial review for build logs without manual checks?

Automated editorial review handles blocking issues via exact replacements, but advisory notes are clearly flagged for human judgment. Cross-reference validation surfaces advisory items requiring manual review.

Does build log genericization work with frontmatter and venture registry data?

Build log genericization cross-references with a venture registry and terminology documentation to validate references. It processes logs containing frontmatter to produce clean, compliant field reports.

What are the limitations of automated build log compliance checking?

Automated build log compliance checking fixes blocking issues via exact replacements but cannot resolve advisory items autonomously. Advisory notes are flagged for human review, requiring manual judgment for nuanced compliance decisions.