agentmako

Category: Tools & Productivity | Uploader: drhalto | Downloads: 0 | Version: v1.0（Latest）

Changelog: Source: GitHub https://github.com/drhalto/agentmako

Directory Structure

Current level: tree/main/mako-ai-claude-plugin/skills/mako-code-intel/

📄 SKILL.md 2.6 KB

SKILL.md

---
description: >-
  TRIGGER when: user wants structural code pattern search (ast-grep) or static
  lint against selected files. Covers `ast_find_pattern`, `lint_files`.
when_to_use: >-
  Use when text search is too weak for a syntax pattern, or when the user wants
  focused diagnostics/static findings for known files.
allowed-tools: "mcp__mako-ai__*"
---

# Mako Code Intel

Use this skill for static code queries that are best answered by syntax-aware
search or diagnostics. It is not the general repo-orientation skill; use
`repo_map` through `/mako-ai:mako-discovery` for that.

## Tools

### `ast_find_pattern`

Use for structural code pattern search over indexed TypeScript, TSX,
JavaScript, and JSX files.

- Best for finding syntax shapes that text search may miss.
- Use for patterns such as function calls, JSX attributes, hook usage,
  imports, conditionals, or unsafe constructs.
- Keep searches bounded with focused patterns and file scopes when possible.
- If the result is a false positive that should not recur, use `finding_ack`
  from `/mako-ai:mako-workflow` with the returned `ackableFingerprint`.

### `lint_files`

Use for focused lint/static diagnostics against selected files.

- Best after editing files or when reviewing a known suspect area.
- Use the returned finding identity/fingerprint when acknowledging reviewed
  diagnostics.
- Do not use `agent_feedback` to suppress a diagnostic; use `finding_ack`.

## Feedback Logging

Log `agent_feedback` when a tool run here was notably useful, partial,
noisy, stale, wrong, or wasted the turn. Skip routine calls.

Required procedure (see `/mako-ai:mako-guide` for full rules and
reason-code vocabulary):

1. Call `recall_tool_runs` to get the prior run's `requestId`. Do not
   fabricate one — if no run is recalled, skip feedback.
2. Call `agent_feedback` with `referencedToolName`,
   `referencedRequestId`, `grade: "full" | "partial" | "no"`,
   `reasonCodes` from the starter vocabulary in `/mako-ai:mako-guide`,
   and a short `reason`.

For individual false-positive or reviewed-accepted static findings from
`ast_find_pattern` or `lint_files`, use `finding_ack` with the returned
`ackableFingerprint` (ast) or `identity.matchBasedId` (lint) — never
`agent_feedback` to suppress static findings. Rate the tool run's
usefulness with `agent_feedback`; mark individual findings with
`finding_ack`. See `/mako-ai:mako-workflow` for `finding_ack` usage.

## See Also

- Use `/mako-ai:mako-discovery` for repo orientation and broad cross-surface
  search.
- Use `/mako-ai:mako-graph` for import impact, cycles, hotspots, and symbols.
- Use `/mako-ai:mako-workflow` for `finding_ack` and finding ack reports.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

agentmako

Directory Structure

SKILL.md

Report

Notice