All authors
Claude Skills by iamalisson
github.com/iamalisson15 skills0 installs9 views
- InquisitorHypothesis-driven problem solving for AI agents. Probe, don't classify. Falsify, don't confirm. Never retry what already failed unchanged. Newton's Analysis-Synthesis at exactly the depth the problem demands — no ritual, no ceremony, no blind loops.Votes: 0GitHub stars: 5
- Speckit Implement'Implement one task from tasks.md, on its own branch and PR (jit-speckit:Votes: 0GitHub stars: 2
- Speckit Jit AnalyzedRecord that analysis ran on the current tasksVotes: 0GitHub stars: 2
- Speckit Jit BranchSwitch to the task's branch before implementingVotes: 0GitHub stars: 2
- Speckit Jit IssuesCreate one GitHub issue per task and open the spec PRVotes: 0GitHub stars: 2
- Speckit Jit PrReview, commit, push and open the task's pull requestVotes: 0GitHub stars: 2
- Speckit Jit ReviewIndependent review of the branch (or of the plan, before issues) by a fresh reader grounded in the whole repositoryVotes: 0GitHub stars: 2
- AdoptAdopt jit-speckit in an existing codebase: read the repo and fill the spec-kit constitution (project, stack, commands, project principles) from what is really there, merging any constitution that already exists. Run after /jit-speckit:init on a repo that already has code.Votes: 0GitHub stars: 2
- HelpExplain jit-speckit from its docs: commands, the feature and task loop, levels, configuration, security, and why things work the way they do. Use for /jit-speckit:help or when the user asks how jit-speckit works.Votes: 0GitHub stars: 2
- InitSet up the current project (new or existing) with spec-kit and jit-speckit: one task = one issue = one branch = one PR, security checks on every commit, push and PR, and best-practice defaults sized by complexity level (lite, standard, full).Votes: 0GitHub stars: 2
- LevelChange a jit-speckit project's complexity level (lite, standard, full): updates the branch flow, the constitution defaults block, the CI and security scaffolding and the git hooks.Votes: 0GitHub stars: 2
- NewStart a new project with jit-speckit: talk through the stack, architecture and infrastructure with the user, catch missing or risky choices (tests, logging, errors, secrets, backups, over-engineering), then set up the project's tooling for any stack (current versions, linters, tests, lockfile, CI, containers) from primary sources, with no application code, prove it runs green, set up jit-speckit, and suggest a foundation spec. Use for /jit-speckit:new or when the user wants to start a project.Votes: 0GitHub stars: 2
- NextShow a spec-kit feature's progress (a task is done when its issue is closed) and start the next open task with /speckit-implement; with several features, asks which. Use when the user asks what's next or has just merged a task PR.Votes: 0GitHub stars: 2
- RemoveRemove jit-speckit from the current project only (the plugin stays in Claude Code): unregisters the spec-kit extension and preset, deletes the files it created, undoes its git hook setup and strips its block from the constitution. Specs and user edits stay. Use for /jit-speckit:remove or when the user wants a clean reinstall.Votes: 0GitHub stars: 2
- SecurityFull security audit of the project: scanners, a manual OWASP Top 10 and CWE Top 25 sweep, business-logic and race-condition flaws, each finding verified, then tracked and fixed safely. Use for /jit-speckit:security, before a release, or when the user asks whether the software is secure.Votes: 0GitHub stars: 2