AI Agent Hub
Back to skills
Full-Stack Dev Assistant icon

Full-Stack Dev Assistant

Development Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md and install @user_fca74304/fullstack-dev.

About this skill

Routine engineering overhead

Full-stack work often slows down not because of core business logic, but because developers keep switching between debugging, comment cleanup, API docs, status updates, and requirement cleanup. fullstack-dev is aimed at standardizing these surrounding development tasks so engineers can spend more time on business implementation and code reasoning.

What it does

It covers five practical workflows:
- Code review and fixes: supports Java, Python, Go, JavaScript/TypeScript, Vue, React, and SQL, then checks syntax issues, logic gaps, redundant code, and performance problems, presenting changes as before/after diffs with line-level reasons.
- Comment generation: adds function descriptions, parameters, return values, exceptions, and key-logic notes in styles such as JSDoc, JavaDoc, and PEP 257, which is useful for legacy code and team handoff.
- Technical docs: produces API docs, database design notes, technical proposals, deployment docs, and lightweight PRDs, mainly in Markdown, with optional OpenAPI-style content.
- Engineering reports: structures daily reports, weekly reports, release summaries, and incident reviews for internal or external audiences.
- Mode switching: use simple mode for explanatory answers or professional mode for direct, senior-level solutions.

Where it fits best

This skill is most useful when you already have a code snippet, API contract, requirement note, or draft report. It does not replace architecture decisions, business prioritization, or production validation. Secrets, internal endpoints, and unverified performance claims still need manual review and desensitization.

Use Cases

  • Debug a Java service snippet for syntax, null-safety, or N+1 query issues and produce before/after fixes.
  • Add PEP 257-style docstrings to an unannotated Python library, covering functions, parameters, returns, and exceptions.
  • Turn API parameters, response shapes, and error codes into a Markdown interface document before frontend integration.
  • Compile release fixes, impact scope, and remaining risks into a weekly report or incident review.

Best For

  • Backend engineers maintaining Java or Go services who need fast debugging and performance triage.
  • Full-stack engineers taking over Vue/React modules and needing comments plus API integration docs.
  • Tech leads who need to turn scattered requirements into lightweight PRDs for frontend-backend alignment.
  • Junior engineers or new hires who need normalized code review, documentation, and weekly reporting.