Daniel Jun Suguimoto
Community@danielsuguimoto · Bauru, SP - Brazil
👋 Hi, I'm Daniel Jun Suguimoto! I'm a software engineer with a passion for web development.
Agent Skills by Daniel Jun Suguimoto
Showing 27 vetted skills indexed across 1 GitHub repositories.
grill-with-codebase
Interrogates a task against the actual codebase to shape a concrete implementation plan.
database
Inspect live database schema, run read-only queries, and execute Eloquent operations via REPL.
adjust
Apply user-requested fixes, improvements, and refactors to existing code without shipping.
code-work
Enforces scoped code reading and minimal editing conventions for code change tasks.
subagents
Gates subagent spawning decisions with dispatch rationales, checklists, and model routing rules.
using-code-navigation
Navigate and refactor code symbols using LSP-backed semantic tools instead of grep.
using-terminal
Enforces safe terminal command execution using configured wrappers and output truncation rules.
knowledge-graph
Convert code, docs, papers, images, and videos into a persistent knowledge graph with community detection.
session-to-memory
Extracts retention-worthy knowledge from session history and persists it to the active memory provider.
ship-changes
Ships current work end-to-end by branching, committing, pushing, and opening a pull request.
triage
Investigate tickets and post read-only findings back to the issue tracker.
setup-skills
Generates project docs spec files for tool configuration through a guided interview.
commit-and-push
Commits staged and unstaged changes with generated messages and pushes to the remote branch.
to-specs
Convert requests or tickets into structured specs and sync them to the ticket system.
pr-fix
Fix pull request review feedback and reply directly to review threads.
pr-create
Creates a pull request for the current branch with template-aware body generation.
memory-usage
Read and write persistent project memory across sessions using topic-based naming conventions.
implement
Implements ticket requirements on an existing feature branch or master with validated code targets.
new-branch
Creates and publishes a categorized git branch from a description, ticket link, or current changes.
draft-reply
Drafts ticket replies grounded in codebase context and posts them as private notes for review.
browser-automation
Automate browser interactions, snapshots, and downloads across logged-in accounts using Playwright-compatible REPL.
caveman
Compresses AI responses by removing filler, hedging, and narration while preserving technical accuracy.
pr-fix-ci
Diagnose and fix failing CI checks on pull requests by reading logs and pushing code fixes.
spawn
Runs a target skill or raw prompt inside an isolated subagent context.
Frequently Asked Questions About Daniel Jun Suguimoto
FAQPage SchemaWhat tasks can I accomplish with danielsuguimoto's skills?▼
You can interrogate tickets into buildable plans, navigate and refactor code via symbol-level LSP navigation, inspect database schemas and run EXPLAIN plans, triage and debug issues read-only, manage branches and pull requests including CI fixes, and persist session learnings into project memory or a knowledge graph.
Who are these skills designed for?▼
Software engineers working on existing codebases who handle tickets, code reviews, and debugging. The skills suit developers wanting structured conventions for code reading, editing, branching, committing, PR creation, review-feedback fixes, and safe terminal and container command execution.
How do I set up and initialize these skills in a project?▼
Invoke the setup-skills skill by saying 'setup skills', 'configure skills', or 'initialize skills'. It creates the <project-root>/docs folder and generates spec files for each skill category, and should be run whenever those docs spec files are missing or incomplete.
How do the skills handle pull requests and code review?▼
Use pr-create to open a pull request for the current branch, or ship-changes to branch, commit, push, and open a PR end-to-end. When review feedback arrives, pr-fix applies code fixes with direct thread responses, and pr-fix-ci resolves failing CI checks.
What are the prerequisites and safety constraints of these skills?▼
context-gathering is mandatory before any code exploration, reading, or editing; subagents gating is mandatory before spawning or large scans. Code navigation requires an LSP-supported language. Triage and draft-reply are strictly read-only, making no code changes or public replies.