Staff Review

Community

c-kick

staff-review

Senior Staff Engineer code review with SOLID principles, security analysis, and architecture critique. Use for significant changes, new systems, or when you want ruthless technical feedback.

Overview

Publisher	c-kick
Repository	`hnl-agent-skills`
Skill name	`staff-review`
Stars	56
Forks	4
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by c-kick on GitHub. Read the source before you install it.

Installation

Install the Staff Review AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/c-kick/hnl-agent-skills/tree/master/staff-review
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/c-kick/hnl-agent-skills.git /tmp/hnl-agent-skills
mkdir -p .claude/skills
cp -r /tmp/hnl-agent-skills/staff-review .claude/skills/staff-review

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Staff Review in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Staff Review on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Staff Review is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Staff Engineer Review

Ruthless architecture, design, and code critique with SOLID principles, core engineering axioms, and OWASP SAMM-informed security practices.

When to Use

New modules, services, or abstractions
Changes to core or shared systems
Security-sensitive code (form handling, user input, authentication)
Significant refactors or new language/framework integrations
Any change you're uncertain about

Review Process

1. Gather Context

First, understand what's being reviewed:

Read the files involved
Identify the scope and boundaries
Check for related code that might be affected

2. Apply Engineering Principles

SOLID:

SRP: One reason to change per module
OCP: Extend via composition; avoid broad rewrites
LSP: Subtypes must be substitutable
ISP: Prefer small, specific interfaces
DIP: Depend on abstractions at boundaries

Core Axioms:

DRY: Single representation of logic/knowledge
KISS: Prefer the simplest design that works
YAGNI: Do not build speculative capability

Quality:

High cohesion, low coupling
Separation of concerns
Law of Demeter (talk to neighbors only)
Fail fast with safe errors

3. Security Review (OWASP SAMM Lens)

Identify data flows and trust boundaries
Check input validation and output encoding
Review authentication/authorization boundaries
Verify secrets handling
Check dependency hygiene

4. Testability Assessment

Can this be unit tested?
Are there clear seams for mocking?
What are the failure modes?

Output Format

Structure your review as:

Verdict: approve / approve-with-changes / block
Top Risks (max 5): ordered by severity
Architecture/Design Critique: boundary choices, data flow, failure modes
Security Review: concrete gaps + suggested controls
Testability: how to prove it works
Actionable Changes: specific edits with rationale

If you block, list the minimum changes needed to unblock.

Critique Rules

Prefer saying "no" to hand-wavy designs
Call out hidden complexity (state management, migrations)
Detect accidental coupling and leaky abstractions
Flag untestable designs and propose seams
Challenge anything that violates YAGNI
Explain the "why" behind every critical note

Example Invocations

/staff-review src/auth/tokenService.js /staff-review lib/core/Registry.php /staff-review “the changes I just made to the payment flow” /staff-review src/components/DataTable/

Frequently asked questions

What does the Staff Review AI skill do?

Senior Staff Engineer code review with SOLID principles, security analysis, and architecture critique. Use for significant changes, new systems, or when you want ruthless technical feedback.

Why use Staff Review on TypingMind?

Because you install it once and use it with any model. Staff Review is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Staff Review in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/c-kick/hnl-agent-skills/tree/master/staff-review. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Staff Review?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Staff Review?

As many as you like. As long as a model supports skills, you can use Staff Review with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Staff Review AI skill free?

It is published on GitHub by c-kick. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Agent Architecture Audit

affaan-m

CommunityPopular

エージェントおよび LLM アプリケーション向けのフルスタック診断。12 層のエージェントスタックにおけるラッパーリグレッション、メモリ汚染、ツール規律の失敗、隠れた修復ループ、レンダリング破損を監査します。重要度順の発見事項とコードファーストの修正を生成します。エージェントアプリケーション、自律ループ、または LLM を活用した機能を構築する開発者に必須です。

Antigravity Cli

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

Backend Code Review

Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests,…

Frontend Code Review

Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Staff Engineer Review

When to Use

Review Process

1. Gather Context

2. Apply Engineering Principles

3. Security Review (OWASP SAMM Lens)

4. Testability Assessment

Output Format

Critique Rules

Example Invocations

Frequently asked questions

Related AI Skills

Set up your own AI workspace now