AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Finding Discipline

skill-jesse-merhi-skills-finding-discipline · by jesse-merhi

Filter code-review observations into actionable findings for PR, cold, security, and noisy-diff reviews; remove style nits and vague risks.

No reviews yet
0 installs
25 views
0.0% view→install

Install

$ agentstack add skill-jesse-merhi-skills-finding-discipline

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jesse-merhi-skills-finding-discipline)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Finding Discipline? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Finding Discipline

Use this skill after you have inspected enough code to know a concrete failure mode. The goal is fewer, sharper findings that a PR author can fix.

Workflow

  1. Check every candidate observation against the finding bar in

[finding-bar.md](references/finding-bar.md).

  1. Drop excluded observations using [exclusions.md](references/exclusions.md).
  2. Run the confirmation pass in [confirmation.md](references/confirmation.md).
  3. Write each finding with the format and severity rules in

[output.md](references/output.md).

  1. Perform the final review pass before presenting findings.

Required Discipline

  • Prefer no finding over a weak finding.
  • Put non-actionable but useful context in residual risk or notes, not findings.
  • Merge duplicates under one root cause.
  • Remove findings that depend on unproven assumptions.
  • Check each line reference still overlaps the reviewed change when possible.
  • Make titles action-oriented, not diagnostic labels.

Context Pointers

  • Use [finding-bar.md](references/finding-bar.md) for the must-pass criteria.
  • Use [exclusions.md](references/exclusions.md) for observations to drop.
  • Use [confirmation.md](references/confirmation.md) before finalizing each

finding.

  • Use [output.md](references/output.md) for finding shape and severity.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.