nestjs-git-commit-pr-message
Prepare NestJS Commits and Pull Requests
Mixed changes and unclear publication requests can produce misleading commits or unintended remote updates. This skill guides verified Git changes and accurate messages within authorized scope.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
Review the Skillstore skill "nestjs-git-commit-pr-message" from https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message.md and its manifest at https://skillstore.io/api/skills/amirtaherkhani-nestjs-git-commit-pr-message/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "nestjs-git-commit-pr-message". Draft a message for a NestJS auth fix that verifies tenant ownership before resource updates.
النتيجة المتوقعة:
- Suggested subject: fix(auth): enforce tenant ownership before resource updates
- Suggested body: Resolve the authenticated tenant and verify ownership before invoking the update use case.
- No commit or remote action performed.
جارٍ استخدام "nestjs-git-commit-pr-message". Commit a configuration update, but the staged environment file contains a live provider token.
النتيجة المتوقعة:
- Commit blocked: the staged environment file contains a plausible provider token.
- No secret value is included in this report.
- Remove the credential and rotate it if exposure may have occurred before resuming.
جارٍ استخدام "nestjs-git-commit-pr-message". Explain the Pages status after a feature branch push when the deployment workflow only runs on main.
النتيجة المتوقعة:
- The feature branch push does not trigger the production Pages workflow.
- Pages will update after an authorized merge or push to main and successful deployment.
- The feature branch push alone does not establish deployment success.
التدقيق الأمني
آمنAll 22 static findings are false positives involving Markdown formatting, example prose, provenance metadata, defensive secret checks, or scoped Git inspection. No evidence found of malicious instructions, credential exfiltration, or unauthorized publication intent. The workflow requires authorization for remote writes and treats fetched issue and pull request text as untrusted.
عوامل الخطر
🌐 الوصول إلى الشبكة (2)
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message?utm_source=security_passport_badge)شارة HTML
<a href="https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/amirtaherkhani-nestjs-git-commit-pr-message/security.svg" alt="Skillstore security assessment" loading="lazy"></a>بطاقة قابلة للتضمين
<iframe src="https://skillstore.io/embed/skills/amirtaherkhani-nestjs-git-commit-pr-message.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>الاستشهادات الأكاديمية (APA · BibTeX · CFF)
اقتباس APA
amirtaherkhani. (2026). nestjs-git-commit-pr-message security audit report (audit version 1) [Author version 2.0.2]. Skillstore. https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message/audits/1اقتباس BibTeX
@techreport{amirtaherkhani-amirtaherkhani-nestjs-git-commit-pr-message-2026,
author = {amirtaherkhani},
title = {nestjs-git-commit-pr-message security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message/audits/1},
note = {Author version 2.0.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nestjs-git-commit-pr-message security audit report (audit version 1)"
version: "2.0.2"
type: report
authors:
- name: "amirtaherkhani"
date-released: "2026-10-04"
url: "https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message/audits/1"
identifiers:
- type: other
value: "skillstore:amirtaherkhani-nestjs-git-commit-pr-message:audit:1"
description: "Skillstore immutable audit report identifier"
تقييم Skillstore
سبب هذا التقييم موثوقية الأدلة: متوسطما الذي يمكنك بناؤه
Commit an isolated NestJS fix
Prepare a verified commit for one feature while preserving unrelated staged and unstaged work.
Prepare a reviewable pull request
Publish an authorized branch update with an accurate summary, compatibility decisions, and actual verification results.
Report release and documentation status
Draft release notes and verify whether the pushed revision triggers CI or GitHub Pages without assuming deployment success.
جرّب هذه الموجّهات
Inspect the staged NestJS changes and draft a commit message matching repository history. Do not commit, push, or modify files.
Commit the NestJS auth fix after relevant checks and staged secret review. Preserve unrelated dashboard changes. Do not push.
Verify the payments feature, commit its intended scope, push to the confirmed remote, and open or update a draft pull request.
Push the verified documentation commit, follow CI for its exact SHA, and report whether Pages updated. Draft release notes without tagging, merging, or publishing.
أفضل الممارسات
- Specify the intended files and whether the task permits committing, pushing, creating a pull request, or preparing release text.
- Review staged changes and relevant check results before authorizing publication.
- Verify the target remote, branch, and exact revision before accepting CI or deployment claims.
تجنب
- Stage every changed file when the worktree includes unrelated edits.
- Include live credentials or personal data in commits, pull request bodies, or verification reports.
- Treat a branch push as permission to merge, release, force-push, or claim a completed deployment.
الأسئلة المتكررة
Does drafting a message create a commit?
Does committing also push the branch?
Are Conventional Commits always required?
What happens when a plausible secret is staged?
What does GitHub integration require?
Does a documentation push always update GitHub Pages?
تفاصيل المطور
المؤلف
amirtaherkhaniالترخيص
MIT
إصدار المؤلف
v2.0.2
مراجعة Skillstore
r1
مرجع
c97a1862d1bc82763903ee068cd15acab35d638c
حداثة الصيانة
٥/١٠/٢٠٢٦
الاستخدام
0 تنزيلات · 0 مشاهدات
بنية الملفات