jnsahaj skills
jnsahaj/skills
Eight skills for code review, draft pull requests and bug triage one cause at a time, waiting for your go-ahead.
- 107 ★ on the repository
- Last commit
Extended access
Why this level
- `create-draft-pr` commits and pushes without an extra prompt.
- `ga` and `ga-pr` start autonomous agent sessions in parallel clones.
Install
- Works in
Manual install
npx skills@latest add jnsahaj/skillsThe only command in the README.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- `create-draft-pr` commits and pushes without an extra prompt.
- `ga` and `ga-pr` start autonomous agent sessions in parallel clones.
This is third-party code. Review the repository files before installing.
What it does
Eight skills the author uses daily. `code-refactor-review` checks a diff for reuse, consistency and slop. `pit-of-success` moves invariants into the interface so the obvious call is the correct one. `zero-tech-debt` reworks a change as if the intended architecture existed from day one. `explain-then-fix` handles bugs one cause at a time: reproduce, explain with a diagram, lay out options and fix only after you say go. `create-draft-pr` commits, pushes and opens a draft PR. `prepare-branch-context` reads the branch diff, `ux-flow-plan` plans from the user flow, and `ga` with `ga-pr` start parallel tmux sessions.
Who it is for. Developers who work through branches and pull requests and want review and refactoring habits captured as skills.
Good fit when
- A diff needs checking for duplicates and drift from neighbouring code before merging.
- A bug is analysed step by step and the fix is approved separately.
- A branch is ready and a draft PR should open with one command.
- You return to someone else's branch and want context fast.
- A feature is first planned as a chain of user actions.
Not a fit when
- The environment has no Git or GitHub CLI.
- You want `ga` and `ga-pr` but the machine lacks the author's `ga` function and tmux.
- The team does not want an agent committing and pushing to branches.
Example request
Review the current branch diff with code-refactor-review and point out duplicates of existing helpers.Limitations
The repository has no license or description, only the list of skills. `ga` and `ga-pr` call the author's personal `ga` command, defaulting to the Pi agent, and fail without it. `create-draft-pr` commits and pushes on its own. Skill texts follow the author's habits; adapt them to your team's rules. The `ga` skill starts the Pi agent by default; Claude Code needs the `--harness c` flag. `create-draft-pr`, `ga-pr` and PR reading need the GitHub CLI `gh`.
How to disable. Delete the skill folders from your agent's skills directory. Branches, commits and draft PRs the skills created are closed and cleaned up separately.
FAQ
How do I install the set?
Run `npx skills@latest add jnsahaj/skills`. The command installs every skill in the repository.
How does `explain-then-fix` differ from a normal bug fix?
The skill changes nothing before you say go. It first reproduces the reporter's own case, explains the cause and lays out fix options.
What does `create-draft-pr` do?
It commits changes, pushes the branch and opens a draft PR with `gh pr create --draft`. On `main` it creates a branch first.
Do `ga` and `ga-pr` work without personal setup?
No. They call the `ga` command from the author's shell and tmux. The other six skills do not depend on that setup.
Is GitHub CLI required?
Yes, for `create-draft-pr`, `ga-pr` and PR reading in `prepare-branch-context`: they call `gh`.
Discussion
No questions or reviews yet.
Related
Skillskyy-logs code-review-skill
code-review-skill
A code review skill with four independent probes, evidence-backed findings and a merge gate derived from JSON
Five slash commands for an agent: a plan before code, memory across sessions, review, failure triage and one UI registry
Two skills: a pull request review where two models argue, and a helper that works through review comments round by round
Twelve standalone skills for development: an agent loop with planning and review, pull request handling, TDD and email triage.
A code review skill across many languages and frameworks: architecture, performance, security, anti-patterns and common bugs
Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| jnsahaj skills (this card) | no | 107 | |
| claude-pr-review | no | 115 | a command runs a PR through five reviewers; here eight independent skills, and bug fixes wait for your go |
| code-review-skill | no | 2,256 | a multi-language review checklist; here review relies on finding existing helpers and neighbouring code style |
README in short
The README is a single install command and a note that the skills are used daily. Descriptions live in each `SKILL.md`.