project

Analyze source code to identify improvement opportunities and generate a structured plan.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/joseph0926/study-all --skill project-joseph0926
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project
Source: https://github.com/joseph0926/study-all/tree/main/.codex/skills/project
Command: npx skills add https://github.com/joseph0926/study-all --skill project-joseph0926

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a project's source code to identify improvement opportunities, generate a structured plan, and support an end-to-end refinement workflow from analysis through validation.

Core Features & Use Cases

  • Phase-driven analysis that surfaces 5 to 8 actionable topics with traceable evidence.
  • Plan generation and tracking by creating and maintaining {project}/.study/plan.md with clear steps and checkpoints.
  • End-to-end workflow support: initialization, area-specific deep dives, discussions, implementation of approved changes, verification, and documentation.

Quick Start

Provide the repository path and an optional area to begin the phase-driven analysis and generate a plan with verification steps.

Frequently Asked Questions about project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze source code to identify maintainability and architecture improvement opportunities?

Source code analysis identifies maintainability and architecture improvement opportunities through phase-driven analysis that surfaces 5 to 8 actionable topics with traceable evidence from the project's repository structure.

What is the best way to structure a code review and track implementation for software engineering projects?

The best way to structure code review tracking is generating and maintaining a {project}/.study/plan.md file that outlines clear steps, checkpoints, and area-specific deep dives for implementation.

Can I use this project improvement workflow on software projects of varying sizes and languages?

Yes, you can apply this project improvement workflow to software projects of varying sizes and languages, guiding structure analysis, area-specific deep-dives, proposal prioritization, implementation, and verification.

How do I generate an actionable improvement plan from a repository path?

Provide the repository path and an optional area to initialize the end-to-end workflow, which performs phase-driven analysis and generates a structured improvement plan with verification steps.

Does the code analysis workflow support documentation and verification after implementing changes?

Yes, the code analysis workflow supports an end-to-end refinement process that includes implementation of approved changes, verification, and traceable documentation using the project's repository structure.