git-linear-automation

git-linear-automation is a cursor rule for Cursor from hexianWeb/Third-Person-MC. It costs 33 tokens per session (355 once invoked), scanned A, original, MIT.

A set of rules for automating Git work and linking commits or pull requests with Linear, a project-management issue tracker.

In plain words
What is it for?
Use it when creating commits, opening or updating Linear issues, adding comments or subtasks, changing issue status or priority, or linking work with GitHub.
Why use it?
It standardizes how changes are grouped, committed, and associated with the correct issue, while also defining how issues and related updates are handled.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when creating commits, opening or updating Linear issues, adding comments or subtasks, changing issue status or priority, or linking work with GitHub.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/hexianweb/third-person-mc/git-linear-automation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/hexianWeb/Third-Person-MC

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for git-linear-automation

README.md
[![agentmods](https://agentmods.dev/badge/rules/hexianweb/third-person-mc/git-linear-automation/github.svg)](https://agentmods.dev/rules/hexianweb/third-person-mc/git-linear-automation)
Your own site
<a href="https://agentmods.dev/rules/hexianweb/third-person-mc/git-linear-automation"><img src="https://agentmods.dev/badge/rules/hexianweb/third-person-mc/git-linear-automation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for git-linear-automation

Your own site · 80×15
<a href="https://agentmods.dev/rules/hexianweb/third-person-mc/git-linear-automation"><img src="https://agentmods.dev/badge/rules/hexianweb/third-person-mc/git-linear-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 355 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00355
Opus 5.5 $0.00013 $0.00142
Sonnet 5.5 $0.00007 $0.00071
Haiku 4.5 $0.00003 $0.00036

Measured 1mo ago against content hash f2efbc71f2b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-linear-automation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/git-linear-automation.mdc · 24 lines

What it actually says

自动化 git 操作与 Linear issue 相关操作标准流程

适用范围

  • 本规则适用于所有涉及 git 版本管理与 Linear issue 协同的开发流程。
  • 适用于团队成员与 AI 助手自动化操作。

1. git 操作

  • 有 staged 文件时,优先将其作为一次 commit。
  • 仅有 unstaged 文件时,需分批 git add,确保每次提交内容与 Linear issue 关联合理,粒度清晰。
  • commit message 必须通过 Linear MCP 获取 issue 详细内容,按 commitizen 规范撰写,结尾加上 Linear issue 及其 GitHub issue 编号。
  • 自动执行 git add、git commit。

2. Linear issue 操作

  • 创建 issue 时自动分配 hexianweb,状态 📝 To Do,优先级中等,label 智能分配。
  • issue 描述自动引用并提取 docs/PRD.md、docs/TD.md 相关内容,丰富 issue 信息,多用 emoji。
  • 支持自动添加评论、子任务、变更状态、调整优先级等。
  • 支持 issue 与 GitHub PR/commit 自动关联。

3. 操作指令

  • 只需告知要提交的文件、关联的 Linear issue(HX-编号)、是否自动生成/更新 issue、评论、子任务等,AI 助手自动完成剩余操作。
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 24 lines · 33 tokens per session scan A f2efbc71f2b2

Subscribe to this mod's changes

git-linear-automation is a cursor rule published in the GitHub repository hexianWeb/Third-Person-MC (195 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 355 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.