mcpField
L
lens-brief

lens-brief

github.com/venhdevOther111 installsUpdated today
Repository

About lens-brief

lens-brief is a skill for producing plain-language technical summaries grounded in repository symbols and paths. It prioritizes the key conclusion, concise active wording, and keeping analysis within scope.

Key features

  1. 01Conclusion-first BLUF structure
  2. 02Plain, concise active-language rules
  3. 03Repository symbol and path anchoring
  4. 04Context isolation without file changes

Use cases

  1. 01Summarizing a technical issue for quick review
  2. 02Explaining repository behavior with concrete code references

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/venhdev/skills --skill lens-brief

After installing, type/lens-briefin Claude Code to confirm it loaded.

Details

From the project README

lens-brief — Controlled Plain-Language Technical Summary Engine

Operating Invariants

  • Language Adaptation: Respond in the caller's active conversational language (e.g., Vietnamese, English).
  • BLUF Primacy: State the decisive conclusion or answer in the opening sentence.
  • Plain Voice (ASD-STE100): Use active voice and short sentences (max 20–25 words); eliminate filler words, phrasal verbs, and passive phrasing.
  • Code Anchoring: Bind terms directly to concrete repository symbols and relative paths (file_path, SymbolName) instead of vague pronouns.
  • Context Isolation: Explain in isolation without modifying files or expanding active scope.

Domain Rubric

1. Plain-Language Translation Matrix (ISO 24495-1)
  • Findable: Lead with the decisive takeaway in the BLUF blockquote so the core message is found instantly.
  • Understandable: Clear, single-meaning words in active sentences instead of bureaucratic phrasing or nominalizations.
  • Usable: State the concrete takeaway or operational action directly in context.
2. Word Choice Guidance (Smell vs. Remedy)
  • Smell (English): "We decided to carry out an asynchronous refactoring of the authentication pipeline."
  • Remedy: "We split AuthService into two background tasks. This prevents login timeouts."
  • Smell (Vietnamese): "Chúng tôi đã tiến hành triển khai thực hiện việc tái cấu trúc bất đồng bộ đối với luồng xác thực."
  • Remedy: "Hệ thống tách AuthService thành hai tác vụ nền để ngăn lỗi timeout đăng nhập."

Canonical Output Contract

> **BLUF**: <Single active sentence stating the core conclusion, change, or answer. Max 20 words.>

<1–3 short paragraphs in plain natural prose. Max 25 words per descriptive sentence, 20 words per procedural sentence. Use active voice and ubiquitous symbols. Explain the context, mechanics, or consequence directly.>

*(omit if purely informational)*
**Next Step**: <Concrete command to execute or decisive choice required from caller.>

Comments

Markdown supported