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.
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
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 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「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 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/amirtaherkhani-nestjs-git-commit-pr-message/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](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/1BibTeX 引用
@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?
開發者詳細資訊
授權
MIT
作者版本
v2.0.2
Skillstore 修訂
r1
引用
c97a1862d1bc82763903ee068cd15acab35d638c
維護新鮮度
2026/10/5
使用量
0 次下載 · 0 次瀏覽