sc-summary✓ ناجح

Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md. Use when asked to add or revise Steering Committee meeting summaries.

٥٦.٦k
★ نجوم
٠
↓ تنزيلات
٣
◉ مشاهدات

// تثبيت المهارة

تثبيت المهارة

المهارات هي كود تابع لأطراف ثالثة من مستودعات GitHub العامة. يفحص SkillHub الأنماط الخبيثة المعروفة، لكنه لا يستطيع ضمان السلامة. راجع الكود المصدري قبل التثبيت.

تثبيت عام (على مستوى المستخدم):

npx skillhub install remix-run/react-router/sc-summary

تثبيت في المشروع الحالي:

npx skillhub install remix-run/react-router/sc-summary --project

skill.install.customTargetHelp

npx skillhub install remix-run/react-router/sc-summary --target-dir /path/to/skills

المسار المقترح: ~/.claude/skills/sc-summary/

محتوى SKILL.md

---
name: sc-summary
description: Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md. Use when asked to add or revise Steering Committee meeting summaries.
---

# Steering Committee Meeting Summaries

Use the notes folder or files the user supplies in the request or current conversation. If no source location is available, ask for it. Write to the repository's `GOVERNANCE.md`, under **Meeting Notes**.

1. Read the existing Meeting Notes entries and list the files at the supplied location. Summarize the requested dates or files. If the user gives no date or quantity, choose the earliest meeting without an entry and do one meeting for review. Do not duplicate an existing entry unless asked to revise it.
2. Read each entire source note, especially the details. Resolve repeated or inconsistent points before writing. Treat proposed ideas, decisions, and suggested next steps distinctly; do not present an unconfirmed proposal as an agreed decision.
3. Write a public-facing, high-level summary of React Router discussion only. Omit unrelated conversation and banter. Refer to participants by first name. Follow the existing `<details>` format and prose in `GOVERNANCE.md`; use short topical headings when useful. Match the depth of existing entries, adjusted to how much substantive discussion occurred.
4. Insert each entry near the other meeting dates, preserve unrelated content, then review the diff against the source and run `git diff --check`. Show the new or revised entries to the user. Do not post them to GitHub, commit, or publish unless requested.

الترخيص

الترخيص المُعلن: MIT

MIT License

Copyright (c) 2014 remix-run

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

عرض الترخيص في المستودع المصدري — النسخة المنشورة هناك هي المرجع.