Generate redo plans from git history and project story files.
npx skills add https://github.com/samwelmunga/JengaAgent --skill redo
Please help me install this Agent Skill. Skill: redo Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/redo Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill redo
This skill solves the issue of fragmented development history by providing a structured way to revisit, rework, or rewrite previously completed tasks, ensuring that code, tests, and documentation remain synchronized.
Use the redo skill to rewrite the authentication middleware identified by commit a1b2c3f to support JWT tokens instead of session tokens.
High-intent search queries and answers about installing and using this skill.
To rewrite existing code, you can map git history and project documentation to specific development tasks. By analyzing commit diffs and epic requirements, this generates comprehensive redo plans that maintain project integrity.
Updating tests and documentation during refactoring requires scanning related files to ensure all dependencies are updated consistently. This approach automatically identifies the original intent and scope of work based on commit SHAs or Epic identifiers.
Impact analysis for architectural transitions scans related files, tests, and documentation to ensure all dependencies are updated during a rewrite. It locates all affected endpoints and creates a structured plan for the transition.
Yes, you need access to git logs and project-specific story files to rework completed tasks. These inputs ensure all affected code, tests, and documentation are synchronized and updated consistently throughout the revision process.
Yes, you can locate all affected endpoints when changing from REST to GraphQL. It helps update corresponding documentation and creates a structured plan for the transition by analyzing commit diffs and epic requirements.
You should avoid using a structured redo plan if you cannot provide access to git logs or project-specific story files. The revision process strictly requires these inputs to map development history and ensure consistent updates across dependencies.
BSteffaniakGenerate Git commit messages from staged changes and write them for commit tools.
jimmymalhanAnalyze file dependencies and test coverage to identify affected files and relevant test suites.
julianobarbosaAutomate Git commits with pre-commit security scans and Conventional Commits enforcement.
Obsidian-OwlAutomate sequential execution of all tasks within a software development epic without manual prompts.
