A command for reading a Linear issue and carrying out its implementation workflow. Linear is a tool for tracking software-development tasks and issues.

Use it to implement a Linear issue, create the required branch, build the project, review the changes, fix critical findings, and commit the result with the issue ID.

It gathers the issue's surrounding context, including parent issues and referenced specifications, before changes begin. It also defines the required build, review, commit, and push steps.

implement — Command by owainlewis

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.

agentmods

npx agentmods add commands/owainlewis/youtube-tutorials/implement

Clone the repo

git clone --depth 1 https://github.com/owainlewis/youtube-tutorials

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 369 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00369
Opus 5	$0.00000	$0.00185
Sonnet 5	$0.00000	$0.00074
Haiku 4.5	$0.00000	$0.00037

Measured 2d ago against content hash 017492c89d8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement 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 2d 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.

tutorials/linear-workflow/resources/examples/.claude/commands/implement.md · 52 lines

What it actually says

Read the Linear issue $ARGUMENTS using the Linear MCP tool.

If the issue has a parent issue, read that too for full context. If the description references a spec file (e.g. Spec: specs/feature.md), read it.

Then follow this workflow:

1. Start

Set the issue status to In Progress.
Create a branch following the convention in CLAUDE.md.

2. Implement

Implement the change described in the ticket.
Run bun run build and confirm it passes.
Commit with the issue ID: <summary> (<ISSUE-ID>)

3. Self-Review

Before pushing, launch a sub-agent with this task:

Review the diff between this branch and main (`git diff main`).

Check for:
- Bugs, logic errors, or edge cases
- Unused imports, dead code, or references to things that don't exist
- Empty catch blocks or swallowed errors
- Security issues (exposed secrets, unsanitized input)
- Over-engineering or unnecessary abstractions
- Missing error handling

For each issue found, classify it as:
- 🔴 Critical — must fix before pushing
- 🟡 Warning — should fix, use judgment
- 🟢 Nit — optional improvement

If no issues found, say "LGTM".

Fix all 🔴 Critical issues. Re-run bun run build after any fixes.

4. Ship

Push and create a PR with gh pr create.
- PR body: summary, verification section, link to Linear issue.
Set the issue status to In Review.
Add a comment on the Linear issue with the PR URL.

If anything fails at any step, stop and report the error.

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.

2d ago First seen · 52 lines · 0 tokens per session scan A 017492c89d8d

Subscribe to this mod's changes

implement is a command published in the GitHub repository owainlewis/youtube-tutorials (365 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 369 tokens. 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.

Code review Git and workflow Learning and teaching agent-skills agentic-coding agentic-engineering ai-engineering claude-code codex

implement

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

1. Start

2. Implement

3. Self-Review

4. Ship

What this file has done since we first saw it

Other commands, from other repositories

workflow-claude-settings

development-workflows

implement

plan

research

workflow-claude-commands