Ss Learn
bitjaru/styleseed
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or…
A skill your agent uses when completing a new feature or making a user-facing change in the apps/extensions workspace to ensure no required files or configurations are forgotten.
Install Finish Extensions Feature
$ npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install senchabot-opensource/monorepo finish-extensions-feature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/senchabot-opensource/monorepo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/finish-extensions-feature .claude/skills/finish-extensions-feature && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "finish-extensions-feature" agent skill from https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-feature into .claude/skills/finish-extensions-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-extensions-feature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-featureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install senchabot-opensource/monorepo finish-extensions-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/senchabot-opensource/monorepo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/finish-extensions-feature .agents/skills/finish-extensions-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "finish-extensions-feature" agent skill from https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-feature into .agents/skills/finish-extensions-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-extensions-feature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install senchabot-opensource/monorepo finish-extensions-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/senchabot-opensource/monorepo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/finish-extensions-feature .cursor/skills/finish-extensions-feature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "finish-extensions-feature" agent skill from https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-feature into .cursor/skills/finish-extensions-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-extensions-feature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/senchabot-opensource/monorepo.git --path .agents/skills/finish-extensions-feature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install senchabot-opensource/monorepo finish-extensions-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/senchabot-opensource/monorepo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/finish-extensions-feature .gemini/skills/finish-extensions-feature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "finish-extensions-feature" agent skill from https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-feature into .gemini/skills/finish-extensions-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-extensions-feature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install senchabot-opensource/monorepo finish-extensions-featureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/senchabot-opensource/monorepo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/finish-extensions-feature .github/skills/finish-extensions-feature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "finish-extensions-feature" agent skill from https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-feature into .github/skills/finish-extensions-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-extensions-feature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install senchabot-opensource/monorepo finish-extensions-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/senchabot-opensource/monorepo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/finish-extensions-feature .opencode/skills/finish-extensions-feature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "finish-extensions-feature" agent skill from https://github.com/senchabot-opensource/monorepo/tree/dev/.agents/skills/finish-extensions-feature into .opencode/skills/finish-extensions-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-extensions-feature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
finish-extensions-feature- GitHub stars
- 114
- Token cost
- ~554 tokens
- SKILL.md length
- 283 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses when completing a new feature or making a user-facing change in the apps/extensions workspace to ensure no required files or configurations are forgotten.
- Works in 6 steps: Translations (en.ts and tr.ts) → Changelog (changelog.ts and i18n) → README.md → …
- Completing a new feature
- SKILL.md covers 1. Translations (en.ts and…, 2. Changelog (changelog.ts and…, 3. README.md and 4. LLM Context Files (llms.txt…, plus 2 more sections
- Calls npm
What it does
Finish Extensions Feature is an agent skill from senchabot-opensource/monorepo. Use this skill when completing a new feature or making a user-facing change in the apps/extensions workspace to ensure no required files or configurations are forgotten.
Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Messaging and chat bots. It works with Next.js, React, Go and TypeScript. The repository describes itself as: Senchabot Community Edition monorepo. Web and bot projects for Senchabot Twitch and Discord bots. The licence is GPL-3.0.
When your agent uses it
- Completing a new feature
- Making a user-facing change in the apps/extensions workspace to ensure no required files
- Configurations are forgotten
Example prompts
- “/finish-extensions-feature”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 41b6206. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Finish Extensions Feature loads about 554 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 283 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from senchabot-opensource/monorepo at commit 41b6206, republished under its GPL-3.0 licence (© senchabot-opensource). 283 words, ~554 tokens.
Download SKILL.mdSave it as
.claude/skills/finish-extensions-feature/SKILL.md (or your agent's skills folder).- name
- finish-extensions-feature
- description
- Use this skill when completing a new feature or making a user-facing change in the apps/extensions workspace to ensure no required files or configurations are forgotten.
Finish Extensions Feature
When you are wrapping up a user-facing change or a new feature in apps/extensions, there are several files that must be updated. CI and tests will fail if these are forgotten.
Follow this checklist:
1. Translations (en.ts and tr.ts)
- Action: Any new UI copy, configuration labels, or settings must be added to both
src/lib/i18n/en.tsandsrc/lib/i18n/tr.ts. - Reason: The build tests require every string key to be present in both locales. Missing a translation in either file will fail
vitest.
2. Changelog (changelog.ts and i18n)
- Action: Add an entry for every user-facing change to
src/lib/changelog.tsat the top of theCHANGELOGarray. - Action: Define the translation key for the changelog entry in both
en.tsandtr.tsunder thechangelog.entriesobject. - Reason: Streamers rely on the changelog to know what's new. Tests will fail if the key is missing in either language.
3. README.md
- Action: If you added new URL parameters to a widget, update the parameter lists in
apps/extensions/README.md. - Action: If you created a whole new widget, add it to the widget list and detailed breakdown sections.
4. LLM Context Files (llms.txt and llms-full.txt)
- Action: Add any new URL parameters or commands to
public/llms-full.txtin the Markdown table for the respective widget. - Action: If you created a new widget or tool, add its summary and link to
public/llms.txtandpublic/llms-full.txt.
5. New Widgets/Tools Only
If your change adds a completely new widget, check these files:
src/lib/widgets.tsorsrc/lib/guides.ts(Title and description, en/tr metadata)src/routes/{-$locale}/(Setup route page)vite.config.ts(Add the English path and the/trpath to the prerender list)public/sitemap.xml
6. Run Tests
- Always run
npm testinsideapps/extensionsafter updating these files to ensure SEO and sitemap tests pass!
© senchabot-opensource, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/finish-extensions-feature of senchabot-opensource/monorepo.
Open the folder on GitHubat commit 41b6206
Compare with similar skills
Finish Extensions Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Finish Extensions Feature this skillsenchabot-opensource/monorepo | 114 | — | ~554 | Automated safety check: Pass | GPL-3.0 | |
| Ss Learnbitjaru/styleseed | 974 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Ultraciteagustinusnathaniel/nextarter-tailwind | 125 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Refactor Reviewkcsujeet/ilamy-calendar | 351 | 2 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Styleseedbitjaru/styleseed | 974 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Release New Versionkcsujeet/ilamy-calendar | 351 | — | ~5.8k | Automated safety check: Pass | MIT |
Similar skills
Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
Code Refactor Review
kcsujeet/ilamy-calendar
Reviews code changes for reuse, composition, codebase consistency, and slop.
Styleseed
bitjaru/styleseed
Build, improve, or inspect UI with StyleSeed. An agent skill from bitjaru/styleseed.
Release New Version
kcsujeet/ilamy-calendar
Cut a new release of @ilamy/calendar — analyze commits since the last tag, suggest a semver bump, draft a CHANGELOG entry in the project's existing style, run the CI gate, commit, tag, push to…
Cleanup Specialist
ahaodev/shadmin
Safe cleanup of Shadmin's Go backend, React frontend, Go CLI, and docs — remove dead code, consolidate duplication, and improve maintainability without changing behavior or adding features.
Related
Categories
Questions about Finish Extensions Feature
What does Finish Extensions Feature do?
A skill your agent uses when completing a new feature or making a user-facing change in the apps/extensions workspace to ensure no required files or configurations are forgotten. Finish Extensions Feature is an agent skill from senchabot-opensource/monorepo. Use this skill when completing a new feature or making a user-facing change in the apps/extensions workspace to ensure no required files or configurations are forgotten.
When should I use Finish Extensions Feature?
Finish Extensions Feature fits situations like: completing a new feature; making a user-facing change in the apps/extensions workspace to ensure no required files; configurations are forgotten.
How do I install Finish Extensions Feature in Claude Code?
Run `npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a claude-code`. Or copy the skill folder (.agents/skills/finish-extensions-feature in senchabot-opensource/monorepo) into .claude/skills/finish-extensions-feature in your project. Claude Code loads it when a task matches its description.
How do I install Finish Extensions Feature in Codex?
Run `npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a codex`. Or copy the skill folder (.agents/skills/finish-extensions-feature in senchabot-opensource/monorepo) into .agents/skills/finish-extensions-feature in your project. Codex loads it when a task matches its description.
Can I use Finish Extensions Feature in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add senchabot-opensource/monorepo --skill finish-extensions-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finish-extensions-feature, .gemini/skills/finish-extensions-feature, .github/skills/finish-extensions-feature and .opencode/skills/finish-extensions-feature in your project.
What does Finish Extensions Feature need to run?
Going by SKILL.md and its folder, Finish Extensions Feature needs the command-line tools its instructions call (npm).
Does Finish Extensions Feature access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Finish Extensions Feature safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Finish Extensions Feature use?
Finish Extensions Feature is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Finish Extensions Feature use?
About 554 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Finish Extensions Feature?
Skills that share tags, products or a category with Finish Extensions Feature: Ss Learn (bitjaru/styleseed, 974 stars), Ultracite (agustinusnathaniel/nextarter-tailwind, 125 stars), Code Refactor Review (kcsujeet/ilamy-calendar, 351 stars) and Styleseed (bitjaru/styleseed, 974 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finish Extensions Feature?
senchabot-opensource (a GitHub organization) maintains it in senchabot-opensource/monorepo, which has 114 GitHub stars. The repository was last updated on October 7, 2026.
Source: senchabot-opensource/monorepo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.